Method and apparatus for PBCH payload in higher frequency ranges

ABSTRACT

Apparatuses and methods for transmitting or receiving a synchronization signals and physical broadcast channel (SS/PBCH) block in a wireless communication system. A method of operating a user equipment (UE) includes receiving a SS/PBCH block, decoding a content of a PBCH in the SS/PBCH block, and determining whether the wireless communication system operates with shared spectrum channel access based on the content of the PBCH. The method further includes determining the content of the PBCH in a first manner based on determining that the wireless communication system operates with shared spectrum channel access or determining the content of the PBCH in a second manner based on determining that the wireless communication system operates without shared spectrum channel access.

CROSS-REFERENCE TO RELATED APPLICATIONS AND CLAIM OF PRIORITY

The present application claims priority to: U.S. Provisional PatentApplication No. 62/964,209, filed on Jan. 22, 2020; U.S. ProvisionalPatent Application No. 62/964,819, filed on Jan. 23, 2020; U.S.Provisional Patent Application No. 63/076,613, filed on Sep. 10, 2020;U.S. Provisional Patent Application No. 63/079,247, filed on Sep. 16,2020; U.S. Provisional Patent Application No. 63/118,508, filed on Nov.25, 2020; and U.S. Provisional Patent Application No. 63/122,242, filedon Dec. 7, 2020. The content of the above-identified patent document isincorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to wireless communicationsystems and, more specifically, the present disclosure relates to aphysical broadcast channel (PBCH) payload design in a higher frequencyrange in a wireless communication system.

BACKGROUND

5th generation (5G) or new radio (NR) mobile communications is recentlygathering increased momentum with all the worldwide technical activitieson the various candidate technologies from industry and academia. Thecandidate enablers for the 5G/NR mobile communications include massiveantenna technologies, from legacy cellular frequency bands up to highfrequencies, to provide beamforming gain and support increased capacity,new waveform (e.g., a new radio access technology (RAT)) to flexiblyaccommodate various services/applications with different requirements,new multiple access schemes to support massive connections, and so on.

SUMMARY

The present disclosure relates to wireless communication systems and,more specifically, the present disclosure relates to a PBCH payloaddesign in a higher frequency range in a wireless communication system.

In one embodiment, a user equipment (UE) in a wireless communicationsystem is provided. The UE includes a transceiver configured to receivea synchronization signals and physical broadcast channel (SS/PBCH) blockand a processor operably connected to the transceiver. The processor isconfigured to decode content of a PBCH in the SS/PBCH block; determinewhether the wireless communication system operates with shared spectrumchannel access based on the content of the PBCH; determine the contentof the PBCH in a first manner, if the wireless communication systemoperates with shared spectrum channel access; and determine the contentof the PBCH in a second manner, if the wireless communication systemoperates without shared spectrum channel access.

In another embodiment, a base station (BS) in a wireless communicationsystem is provided. The BS includes a processor configured to determinewhether the wireless communication system operates with shared spectrumchannel access; configure content of a physical broadcast channel (PBCH)according to a first manner, if the wireless communication systemoperates with shared spectrum channel access; configure the content ofthe PBCH according to a second manner, if the wireless communicationsystem operates without shared spectrum channel access; and encode theconfigured content of the PBCH in a synchronization signals and physicalbroadcast channel (SS/PBCH) block. The BS also includes a transceiveroperably connected to the processor. The transceiver is configured totransmit the SS/PBCH block over downlink channels.

In yet another embodiment, a method of a UE in a wireless communicationsystem is provided. The method includes receiving a SS/PBCH block,decoding a content of a PBCH in the SS/PBCH block, and determiningwhether the wireless communication system operates with shared spectrumchannel access based on the content of the PBCH. The method furtherincludes determining the content of the PBCH in a first manner based ondetermining that the wireless communication system operates with sharedspectrum channel access or determining the content of the PBCH in asecond manner based on determining that the wireless communicationsystem operates without shared spectrum channel access.

Other technical features may be readily apparent to one skilled in theart from the following figures, descriptions, and claims.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document. The term “couple” and its derivativesrefer to any direct or indirect communication between two or moreelements, whether or not those elements are in physical contact with oneanother. The terms “transmit,” “receive,” and “communicate,” as well asderivatives thereof, encompass both direct and indirect communication.The terms “include” and “comprise,” as well as derivatives thereof, meaninclusion without limitation. The term “or” is inclusive, meaningand/or. The phrase “associated with,” as well as derivatives thereof,means to include, be included within, interconnect with, contain, becontained within, connect to or with, couple to or with, be communicablewith, cooperate with, interleave, juxtapose, be proximate to, be boundto or with, have, have a property of, have a relationship to or with, orthe like. The term “controller” means any device, system, or partthereof that controls at least one operation. Such a controller may beimplemented in hardware or a combination of hardware and software and/orfirmware. The functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely. Thephrase “at least one of,” when used with a list of items, means thatdifferent combinations of one or more of the listed items may be used,and only one item in the list may be needed. For example, “at least oneof: A, B, and C” includes any of the following combinations: A, B, C, Aand B, A and C, B and C, and A and B and C.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for other certain words and phrases are provided throughoutthis patent document. Those of ordinary skill in the art shouldunderstand that in many if not most instances, such definitions apply toprior as well as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 illustrates an example wireless network according to embodimentsof the present disclosure;

FIG. 2 illustrates an example gNB according to embodiments of thepresent disclosure;

FIG. 3 illustrates an example UE according to embodiments of the presentdisclosure;

FIGS. 4 and 5 illustrate example wireless transmit and receive pathsaccording to this disclosure;

FIG. 6 illustrates an example overlapping band with and without sharedspectrum channel access according to embodiments of the presentdisclosure;

FIG. 7 illustrates a flowchart of a method for an indication ofoperation with shared spectrum channel access or not according toembodiments of the present disclosure;

FIG. 8 illustrates example multiplexing patterns between SSB and CORESET#0 according to embodiments of the present disclosure;

FIG. 9 illustrates an example second type of channelization andsynchronization raster according to embodiments of the presentdisclosure;

FIG. 10 illustrates an example CORESET #0 BW for pattern 1 according toembodiments of the present disclosure;

FIG. 11 illustrates an example pattern 2 according to embodiments of thepresent disclosure;

FIG. 12 illustrates an example CORESET #0 BW for pattern 2 or pattern 3according to embodiments of the present disclosure;

FIG. 13 illustrates an example pattern 3 according to embodiments of thepresent disclosure;

FIG. 14 illustrates an example carrier aggregation to achieve largebandwidth according to embodiments of the present disclosure;

FIG. 15 illustrates an example set of narrow carriers to constructwideband using carrier aggregation according to embodiments of thepresent disclosure;

FIG. 16 illustrates an example synchronization raster design forunlicensed and licensed operations according to embodiments of thepresent disclosure;

FIG. 17A illustrates an example cross-carrier indication for CORESET #0according to embodiments of the present disclosure;

FIG. 17B illustrates another example cross-carrier indication forCORESET #0 according to embodiments of the present disclosure; and

FIG. 18 illustrates a flow chart of a method for determining PBCHcontent according to embodiments of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 through FIG. 18 , discussed below, and the various embodimentsused to describe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

The following documents are hereby incorporated by reference into thepresent disclosure as if fully set forth herein: 3GPP TS 38.211 v15.7.0,“NR; Physical channels and modulation”; 3GPP TS 38.212 v15.7.0, “NR;Multiplexing and Channel coding”; 3GPP TS 38.213 v15.7.0, “NR; PhysicalLayer Procedures for Control”; 3GPP TS 38.214 v15.7.0, “NR; PhysicalLayer Procedures for Data”; and 3GPP TS 38.331 v15.7.0, “NR; RadioResource Control (RRC) protocol specification.”

FIGS. 1-3 below describe various embodiments implemented in wirelesscommunications systems and with the use of orthogonal frequency divisionmultiplexing (OFDM) or orthogonal frequency division multiple access(OFDMA) communication techniques. The descriptions of FIGS. 1-3 are notmeant to imply physical or architectural limitations to the manner inwhich different embodiments may be implemented. Different embodiments ofthe present disclosure may be implemented in any suitably-arrangedcommunications system.

FIG. 1 illustrates an example wireless network according to embodimentsof the present disclosure. The embodiment of the wireless network shownin FIG. 1 is for illustration only. Other embodiments of the wirelessnetwork 100 could be used without departing from the scope of thisdisclosure.

As shown in FIG. 1 , the wireless network includes a gNB 101 (e.g., basestation, BS), a gNB 102, and a gNB 103. The gNB 101 communicates withthe gNB 102 and the gNB 103. The gNB 101 also communicates with at leastone network 130, such as the Internet, a proprietary Internet Protocol(IP) network, or other data network.

The gNB 102 provides wireless broadband access to the network 130 for afirst plurality of user equipments (UEs) within a coverage area 120 ofthe gNB 102. The first plurality of UEs includes a UE 111, which may belocated in a small business; a UE 112, which may be located in anenterprise (E); a UE 113, which may be located in a WiFi hotspot (HS); aUE 114, which may be located in a first residence (R); a UE 115, whichmay be located in a second residence (R); and a UE 116, which may be amobile device (M), such as a cell phone, a wireless laptop, a wirelessPDA, or the like. The gNB 103 provides wireless broadband access to thenetwork 130 for a second plurality of UEs within a coverage area 125 ofthe gNB 103. The second plurality of UEs includes the UE 115 and the UE116. In some embodiments, one or more of the gNBs 101-103 maycommunicate with each other and with the UEs 111-116 using 5G/NR, LTE,LTE-A, WiMAX, WiFi, or other wireless communication techniques.

Depending on the network type, the term “base station” or “BS” can referto any component (or collection of components) configured to providewireless access to a network, such as transmit point (TP),transmit-receive point (TRP), an enhanced base station (eNodeB or eNB),a 5G/NR base station (gNB), a macrocell, a femtocell, a WiFi accesspoint (AP), or other wirelessly enabled devices. Base stations mayprovide wireless access in accordance with one or more wirelesscommunication protocols, e.g., 5G/NR 3GPP NR, long term evolution (LTE),LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi802.11a/b/g/n/ac, etc. For the sake of convenience, the terms “BS” and“TRP” are used interchangeably in this patent document to refer tonetwork infrastructure components that provide wireless access to remoteterminals. Also, depending on the network type, the term “userequipment” or “UE” can refer to any component such as “mobile station,”“subscriber station,” “remote terminal,” “wireless terminal,” “receivepoint,” or “user device.” For the sake of convenience, the terms “userequipment” and “UE” are used in this patent document to refer to remotewireless equipment that wirelessly accesses a BS, whether the UE is amobile device (such as a mobile telephone or smartphone) or is normallyconsidered a stationary device (such as a desktop computer or vendingmachine).

Dotted lines show the approximate extents of the coverage areas 120 and125, which are shown as approximately circular for the purposes ofillustration and explanation only. It should be clearly understood thatthe coverage areas associated with gNBs, such as the coverage areas 120and 125, may have other shapes, including irregular shapes, dependingupon the configuration of the gNBs and variations in the radioenvironment associated with natural and man-made obstructions.

As described in more detail below, one or more of the UEs 111-116include circuitry, programing, or a combination thereof, for beammanagement and coverage enhancements for semi-persistent and configuredgrant transmission. In certain embodiments, and one or more of the gNBs101-103 includes circuitry, programing, or a combination thereof, forbeam management and coverage enhancements for semi-persistent andconfigured grant transmission.

Although FIG. 1 illustrates one example of a wireless network, variouschanges may be made to FIG. 1 . For example, the wireless network couldinclude any number of gNBs and any number of UEs in any suitablearrangement. Also, the gNB 101 could communicate directly with anynumber of UEs and provide those UEs with wireless broadband access tothe network 130. Similarly, each gNB 102-103 could communicate directlywith the network 130 and provide UEs with direct wireless broadbandaccess to the network 130. Further, the gNBs 101, 102, and/or 103 couldprovide access to other or additional external networks, such asexternal telephone networks or other types of data networks.

FIG. 2 illustrates an example gNB 102 according to embodiments of thepresent disclosure. The embodiment of the gNB 102 illustrated in FIG. 2is for illustration only, and the gNBs 101 and 103 of FIG. 1 could havethe same or similar configuration. However, gNBs come in a wide varietyof configurations, and FIG. 2 does not limit the scope of thisdisclosure to any particular implementation of a gNB.

As shown in FIG. 2 , the gNB 102 includes multiple antennas 205 a-205 n,multiple RF transceivers 210 a-210 n, transmit (TX) processing circuitry215, and receive (RX) processing circuitry 220. The gNB 102 alsoincludes a controller/processor 225, a memory 230, and a backhaul ornetwork interface 235.

The RF transceivers 210 a-210 n receive, from the antennas 205 a-205 n,incoming RF signals, such as signals transmitted by UEs in the network100. The RF transceivers 210 a-210 n down-convert the incoming RFsignals to generate IF or baseband signals. The IF or baseband signalsare sent to the RX processing circuitry 220, which generates processedbaseband signals by filtering, decoding, and/or digitizing the basebandor IF signals. The RX processing circuitry 220 transmits the processedbaseband signals to the controller/processor 225 for further processing.

The TX processing circuitry 215 receives analog or digital data (such asvoice data, web data, e-mail, or interactive video game data) from thecontroller/processor 225. The TX processing circuitry 215 encodes,multiplexes, and/or digitizes the outgoing baseband data to generateprocessed baseband or IF signals. The RF transceivers 210 a-210 nreceive the outgoing processed baseband or IF signals from the TXprocessing circuitry 215 and up-converts the baseband or IF signals toRF signals that are transmitted via the antennas 205 a-205 n.

The controller/processor 225 can include one or more processors or otherprocessing devices that control the overall operation of the gNB 102.For example, the controller/processor 225 could control the reception offorward channel signals and the transmission of reverse channel signalsby the RF transceivers 210 a-210 n, the RX processing circuitry 220, andthe TX processing circuitry 215 in accordance with well-knownprinciples. The controller/processor 225 could support additionalfunctions as well, such as more advanced wireless communicationfunctions. For instance, the controller/processor 225 could support beamforming or directional routing operations in which outgoing/incomingsignals from/to multiple antennas 205 a-205 n are weighted differentlyto effectively steer the outgoing signals in a desired direction. Any ofa wide variety of other functions could be supported in the gNB 102 bythe controller/processor 225.

The controller/processor 225 is also capable of executing programs andother processes resident in the memory 230, such as an OS. Thecontroller/processor 225 can move data into or out of the memory 230 asrequired by an executing process.

The controller/processor 225 is also coupled to the backhaul or networkinterface 235. The backhaul or network interface 235 allows the gNB 102to communicate with other devices or systems over a backhaul connectionor over a network. The interface 235 could support communications overany suitable wired or wireless connection(s). For example, when the gNB102 is implemented as part of a cellular communication system (such asone supporting 5G/NR, LTE, or LTE-A), the interface 235 could allow thegNB 102 to communicate with other gNBs over a wired or wireless backhaulconnection. When the gNB 102 is implemented as an access point, theinterface 235 could allow the gNB 102 to communicate over a wired orwireless local area network or over a wired or wireless connection to alarger network (such as the Internet). The interface 235 includes anysuitable structure supporting communications over a wired or wirelessconnection, such as an Ethernet or RF transceiver.

The memory 230 is coupled to the controller/processor 225. Part of thememory 230 could include a RAM, and another part of the memory 230 couldinclude a Flash memory or other ROM.

Although FIG. 2 illustrates one example of gNB 102, various changes maybe made to FIG. 2 . For example, the gNB 102 could include any number ofeach component shown in FIG. 2 . As a particular example, an accesspoint could include a number of interfaces 235, and thecontroller/processor 225 could support routing functions to route databetween different network addresses. As another particular example,while shown as including a single instance of TX processing circuitry215 and a single instance of RX processing circuitry 220, the gNB 102could include multiple instances of each (such as one per RFtransceiver). Also, various components in FIG. 2 could be combined,further subdivided, or omitted and additional components could be addedaccording to particular needs.

FIG. 3 illustrates an example UE 116 according to embodiments of thepresent disclosure. The embodiment of the UE 116 illustrated in FIG. 3is for illustration only, and the UEs 111-115 of FIG. 1 could have thesame or similar configuration. However, UEs come in a wide variety ofconfigurations, and FIG. 3 does not limit the scope of this disclosureto any particular implementation of a UE.

As shown in FIG. 3 , the UE 116 includes an antenna 305, a radiofrequency (RF) transceiver 310, TX processing circuitry 315, amicrophone 320, and RX processing circuitry 325. The UE 116 alsoincludes a speaker 330, a processor 340, an input/output (I/O) interface(IF) 345, a touchscreen 350, a display 355, and a memory 360. The memory360 includes an operating system (OS) 361 and one or more applications362.

The RF transceiver 310 receives, from the antenna 305, an incoming RFsignal transmitted by a gNB of the network 100. The RF transceiver 310down-converts the incoming RF signal to generate an intermediatefrequency (IF) or baseband signal. The IF or baseband signal is sent tothe RX processing circuitry 325, which generates a processed basebandsignal by filtering, decoding, and/or digitizing the baseband or IFsignal. The RX processing circuitry 325 transmits the processed basebandsignal to the speaker 330 (such as for voice data) or to the processor340 for further processing (such as for web browsing data).

The TX processing circuitry 315 receives analog or digital voice datafrom the microphone 320 or other outgoing baseband data (such as webdata, e-mail, or interactive video game data) from the processor 340.The TX processing circuitry 315 encodes, multiplexes, and/or digitizesthe outgoing baseband data to generate a processed baseband or IFsignal. The RF transceiver 310 receives the outgoing processed basebandor IF signal from the TX processing circuitry 315 and up-converts thebaseband or IF signal to an RF signal that is transmitted via theantenna 305.

The processor 340 can include one or more processors or other processingdevices and execute the OS 361 stored in the memory 360 in order tocontrol the overall operation of the UE 116. For example, the processor340 could control the reception of forward channel signals and thetransmission of reverse channel signals by the RF transceiver 310, theRX processing circuitry 325, and the TX processing circuitry 315 inaccordance with well-known principles. In some embodiments, theprocessor 340 includes at least one microprocessor or microcontroller.

The processor 340 is also capable of executing other processes andprograms resident in the memory 360, such as processes for beammanagement. The processor 340 can move data into or out of the memory360 as required by an executing process. In some embodiments, theprocessor 340 is configured to execute the applications 362 based on theOS 361 or in response to signals received from gNBs or an operator. Theprocessor 340 is also coupled to the I/O interface 345, which providesthe UE 116 with the ability to connect to other devices, such as laptopcomputers and handheld computers. The I/O interface 345 is thecommunication path between these accessories and the processor 340.

The processor 340 is also coupled to the touchscreen 350 and the display355. The operator of the UE 116 can use the touchscreen 350 to enterdata into the UE 116. The display 355 may be a liquid crystal display,light emitting diode display, or other display capable of rendering textand/or at least limited graphics, such as from web sites.

The memory 360 is coupled to the processor 340. Part of the memory 360could include a random access memory (RAM), and another part of thememory 360 could include a Flash memory or other read-only memory (ROM).

Although FIG. 3 illustrates one example of UE 116, various changes maybe made to FIG. 3 . For example, various components in FIG. 3 could becombined, further subdivided, or omitted and additional components couldbe added according to particular needs. As a particular example, theprocessor 340 could be divided into multiple processors, such as one ormore central processing units (CPUs) and one or more graphics processingunits (GPUs). Also, while FIG. 3 illustrates the UE 116 configured as amobile telephone or smartphone, UEs could be configured to operate asother types of mobile or stationary devices.

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems and to enable various verticalapplications, efforts have been made to develop and deploy an improved5G/NR or pre-5G/NR communication system. Therefore, the 5G/NR orpre-5G/NR communication system is also called a “beyond 4G network” or a“post LTE system.” The 5G/NR communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60 GHzbands, so as to accomplish higher data rates or in lower frequencybands, such as 6 GHz, to enable robust coverage and mobility support.Examples of the present disclosure may also be applied to deployment of5G communication system, 6G or even later release which may useterahertz (THz) bands. To decrease propagation loss of the radio wavesand increase the transmission distance, the beamforming, massivemultiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO),array antenna, an analog beam forming, large scale antenna techniquesare discussed in 5G/NR communication systems.

In addition, in 5G/NR communication systems, development for systemnetwork improvement is under way based on advanced small cells, cloudradio access networks (RANs), ultra-dense networks, device-to-device(D2D) communication, wireless backhaul, moving network, cooperativecommunication, coordinated multi-points (CoMP), reception-endinterference cancellation and the like.

A communication system includes a downlink (DL) that refers totransmissions from a base station or one or more transmission points toUEs and an uplink (UL) that refers to transmissions from UEs to a basestation or to one or more reception points.

A time unit for DL signaling or for UL signaling on a cell is referredto as a slot and can include one or more symbols. A symbol can alsoserve as an additional time unit. A frequency (or bandwidth (BW)) unitis referred to as a resource block (RB). One RB includes a number ofsub-carriers (SCs). For example, a slot can have duration of 0.5milliseconds or 1 millisecond, include 14 symbols and an RB can include12 SCs with inter-SC spacing of 15 KHz or 30 KHz, and so on.

DL signals include data signals conveying information content, controlsignals conveying DL control information (DCI), and reference signals(RS) that are also known as pilot signals. A gNB transmits datainformation or DCI through respective physical DL shared channels(PDSCHs) or physical DL control channels (PDCCHs). A PDSCH or a PDCCHcan be transmitted over a variable number of slot symbols including oneslot symbol. For brevity, a DCI format scheduling a PDSCH reception by aUE is referred to as a DL DCI format and a DCI format scheduling aphysical uplink shared channel (PUSCH) transmission from a UE isreferred to as an UL DCI format.

A gNB transmits one or more of multiple types of RS including channelstate information RS (CSI-RS) and demodulation RS (DMRS). A CSI-RS isprimarily intended for UEs to perform measurements and provide channelstate information (CSI) to a gNB. For channel measurement, non-zeropower CSI-RS (NZP CSI-RS) resources are used. For interferencemeasurement reports (IMRs), CSI interference measurement (CSI-IM)resources associated with a zero power CSI-RS (ZP CSI-RS) configurationare used. A CSI process includes NZP CSI-RS and CSI-IM resources.

A UE can determine CSI-RS transmission parameters through DL controlsignaling or higher layer signaling, such as radio resource control(RRC) signaling, from a gNB. Transmission instances of a CSI-RS can beindicated by DL control signaling or be configured by higher layersignaling. A DMRS is transmitted only in the BW of a respective PDCCH orPDSCH and a UE can use the DMRS to demodulate data or controlinformation.

FIG. 4 and FIG. 5 illustrate example wireless transmit and receive pathsaccording to this disclosure. In the following description, a transmitpath 400 may be described as being implemented in a gNB (such as the gNB102), while a receive path 500 may be described as being implemented ina UE (such as a UE 116). However, it may be understood that the receivepath 500 can be implemented in a gNB and that the transmit path 400 canbe implemented in a UE. In some embodiments, the receive path 500 isconfigured to support the codebook design and structure for systemshaving 2D antenna arrays as described in embodiments of the presentdisclosure.

The transmit path 400 as illustrated in FIG. 4 includes a channel codingand modulation block 405, a serial-to-parallel (S-to-P) block 410, asize N inverse fast Fourier transform (IFFT) block 415, aparallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425,and an up-converter (UC) 430. The receive path 500 as illustrated inFIG. 5 includes a down-converter (DC) 555, a remove cyclic prefix block560, a serial-to-parallel (S-to-P) block 565, a size N fast Fouriertransform (FFT) block 570, a parallel-to-serial (P-to-S) block 575, anda channel decoding and demodulation block 580.

As illustrated in FIG. 400 , the channel coding and modulation block 405receives a set of information bits, applies coding (such as alow-density parity check (LDPC) coding), and modulates the input bits(such as with quadrature phase shift keying (QPSK) or quadratureamplitude modulation (QAM)) to generate a sequence of frequency-domainmodulation symbols.

The serial-to-parallel block 410 converts (such as de-multiplexes) theserial modulated symbols to parallel data in order to generate Nparallel symbol streams, where N is the IFFT/FFT size used in the gNB102 and the UE 116. The size N IFFT block 415 performs an IFFT operationon the N parallel symbol streams to generate time-domain output signals.The parallel-to-serial block 420 converts (such as multiplexes) theparallel time-domain output symbols from the size N IFFT block 415 inorder to generate a serial time-domain signal. The add cyclic prefixblock 425 inserts a cyclic prefix to the time-domain signal. Theup-converter 430 modulates (such as up-converts) the output of the addcyclic prefix block 425 to an RF frequency for transmission via awireless channel. The signal may also be filtered at baseband beforeconversion to the RF frequency.

A transmitted RF signal from the gNB 102 arrives at the UE 116 afterpassing through the wireless channel, and reverse operations to those atthe gNB 102 are performed at the UE 116.

As illustrated in FIG. 5 , the down-converter 555 down-converts thereceived signal to a baseband frequency, and the remove cyclic prefixblock 560 removes the cyclic prefix to generate a serial time-domainbaseband signal. The serial-to-parallel block 565 converts thetime-domain baseband signal to parallel time domain signals. The size NFFT block 570 performs an FFT algorithm to generate N parallelfrequency-domain signals. The parallel-to-serial block 575 converts theparallel frequency-domain signals to a sequence of modulated datasymbols. The channel decoding and demodulation block 580 demodulates anddecodes the modulated symbols to recover the original input data stream.

Each of the gNBs 101-103 may implement a transmit path 400 asillustrated in FIG. 4 that is analogous to transmitting in the downlinkto UEs 111-116 and may implement a receive path 500 as illustrated inFIG. 5 that is analogous to receiving in the uplink from UEs 111-116.Similarly, each of UEs 111-116 may implement the transmit path 400 fortransmitting in the uplink to the gNBs 101-103 and may implement thereceive path 500 for receiving in the downlink from the gNBs 101-103.

Each of the components in FIG. 4 and FIG. 5 can be implemented usingonly hardware or using a combination of hardware and software/firmware.As a particular example, at least some of the components in FIG. 4 andFIG. 5 may be implemented in software, while other components may beimplemented by configurable hardware or a mixture of software andconfigurable hardware. For instance, the FFT block 570 and the IFFTblock 515 may be implemented as configurable software algorithms, wherethe value of size N may be modified according to the implementation.

Furthermore, although described as using FFT and IFFT, this is by way ofillustration only and may not be construed to limit the scope of thisdisclosure. Other types of transforms, such as discrete Fouriertransform (DFT) and inverse discrete Fourier transform (IDFT) functions,can be used. It may be appreciated that the value of the variable N maybe any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFTfunctions, while the value of the variable N may be any integer numberthat is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT andIFFT functions.

Although FIG. 4 and FIG. 5 illustrate examples of wireless transmit andreceive paths, various changes may be made to FIG. 4 and FIG. 5 . Forexample, various components in FIG. 4 and FIG. 5 can be combined,further subdivided, or omitted and additional components can be addedaccording to particular needs. Also, FIG. 4 and FIG. 5 are meant toillustrate examples of the types of transmit and receive paths that canbe used in a wireless network. Any other suitable architectures can beused to support wireless communications in a wireless network.

The present disclosure focuses on the PBCH payload design for higherfrequency range, in order to support potentially larger number ofcandidate synchronization signal/physical broadcasting channel (SS/PBCH)blocks. Related required changes for the interleaving of PBCH payload,the scrambling of PBCH payload, and the demodulation-reference signal(DM-RS) sequence of PBCH are also specified in this disclosure.

The present disclosure includes the following components and examples:indication using bits generated from physical layer, including examplesof increasing the PHY bits, re-interpret the PHY bits, and restructuremaster information block (MIB) and PHY bits; an indication of a quasico-locate (QCL) parameter in PBCH payload; an indication of operationwith or without shared spectrum channel access in PBCH payload; andindication of k_SSB; an indication of the 4th least significant bits(LSB) of system frame number (SFN) in MIB of the PBCH payload;corresponding changes to the interleaving of PBCH payload; correspondingchanges to the scrambling of PBCH payload; and corresponding changes tothe DM-RS sequences of PBCH payload.

In NR Rel-15 and Rel-16, PBCH payload comprises 24 bits from higherlayer, and 8 bits from physical layer, wherein the 24 bits from higherlayer include MIB of 23 bits (as summarized in TABLE 1) and one MIBextension bit. The 8 bits from physical layer, denoted by ā_(Ā), ā_(Ā+1), ā_(Ā+2) , ā_(Ā+3) , ā_(Ā+4) , ā_(Ā+5) , ā_(Ā+6) , and ā_(Ā+7) , referto the timing information within 16 radio frames, as summarized in TABLE2.

TABLE 1 MIB of NR Rel-15 and Rel-16 Number Field Value of bitssystemFrameNumber BIT STRING (SIZE (6)) 6 subCarrierSpacingCommonENUMERATED {scs15or60, 1 scs30or120} ssb-SubcarrierOffset INTEGER(0..15) 4 dmrs-TypeA-Position ENUMERATED {pos2, pos3} 1 pdcch-ConfigSIB1PDCCH-ConfigSIB1 8 cellBarred ENUMERATED {barred, 1 notBarred)intraFreqReselection ENUMERATED {allowed, 1 notAllowed} spare BIT STRING(SIZE (1)) 1

TABLE 2 Physical layer parameters in PBCH payload of NR Rel-15 andRel-16 L _(max) = 4 or 8 L _(max) = 10 L _(max) = 20 L _(max) = 64 Bit(Rel-15) (Rel-16) (Rel-16) (Rel-15) ā _(A) 4th LSB of 4th LSB of 4th LSBof 4th LSB of SFN SFN SFN SFN ā _(A) +1 3rd LSB of 3rd LSB of 3rd LSB of3rd LSB of SFN SFN SFN SFN ā _(A) +2 2nd LSB of 2nd LSB of 2nd LSB of2nd LSB of SFN SFN SFN SFN ā _(A) +3 1st LSB of 1st LSB of 1st LSB of1st LSB of SFN SFN SFN SFN ā _(A) +4 Half frame Half frame Half frameHalf frame bit bit bit bit ā _(A) +5 MSB of k_(SSB) MSB of k_(SSB) MSBof k_(SSB) 6th LSB of candidate SSB index ā _(A) +6 reserved reserved5th LSB of 5th LSB of candidate candidate SSB index SSB index ā _(A) +7reserved 4th LSB of 4th LSB of 4th LSB of candidate candidate candidateSSB index SSB index SSB index

For a new carrier frequency range between 52.6 GHz and 71 GHz, a newnumerology at least with a larger subcarrier spacing could be supported,to accommodate the larger phase noise and larger carrier bandwidth. Whena new numerology (e.g., including a new subcarrier spacing) is supportedin NR, the timing indication and the corresponding PBCH payload designmay need to be enhanced in order to support such new numerology. Thisdisclosure specifies the details of PBCH payload for higher frequencyrange, wherein the higher frequency range at least includes the carrierfrequency range between 52.6 GHz and 71 GHz, and can be applicable toboth licensed (e.g., operated without shared spectrum channel access)and unlicensed bands (e.g., operated with shared spectrum channelaccess) in the frequency range.

Although exemplary descriptions and embodiments to follow assume OFDM orOFDMA, this disclosure can be extended to other OFDM-based transmissionwaveforms or multiple access schemes such as filtered OFDM (F-OFDM).

In one embodiment, there can be more than 64 candidate SS/PBCH blockswithin a predefined time period (e.g., half frame), e.g., L _(max)>64,and there is a need to indicate the 7th LSB of the candidate SS/PBCHblock index in the payload of PBCH. In one example, the supporting of L_(max)>64 is only applicable to a subcarrier spacing (SCS) of theSS/PBCH block larger than 120 kHz (e.g., 480 kHz and/or 960 kHz), suchthat example on indicating the 7th LSB of the candidate SS/PBCH blockindex in the payload of PBCH as described in this disclosure is onlyapplicable to the corresponding SCS.

In one embodiment, the PHY bits are increased. In one embodiment, forthe higher carrier frequency range considered in this disclosure, thenumber of bits in the PBCH payload provided by higher layer maintainsthe same as NR Rel-15 and Rel-16, and the number of bits in the PBCHpayload generated by the physical layer increases from 8 to 8+X (e.g.,increased from NR Rel-15 and Rel-16), where X is a positive integer.

In one example, the extra X bits corresponding to the timing informationrelated to enlarged maximum number of candidate SS/PBCH block locationswithin a half frame, e.g., the extra most significant bits (MSBs) of thecandidate synchronization signal block (SSB, SS/PBCH block) index. Forone instance, if L _(max)>64, then X=┌log₂ L _(max)▴−6. Examples areshown in TABLE 3.

TABLE 3 Example increased number of bits in PBCH. L _(max) X Examplebits 80 1 ā _(A) +8 128 1 ā _(A) +8 160 2 ā _(A) +8, ā _(A) +9 256 2 ā_(A) +8, ā _(A) +9 320 3 ā _(A) +8, ā _(A) +9, ā _(A) +10 512 3 ā _(A)+8, ā _(A) +9, ā _(A) +10

In one example, the extra X bits corresponding to the timing informationrelated to enlarged maximum number of candidate SS/PBCH block locationswithin a half frame, e.g., the extra MSBs of the candidate SSB index,and the indication of parameter for QCL information. For one instance,if L _(max)>64, then X=┌log₂ L _(max)┐−3. Examples are shown in TABLE 4.

TABLE 4 Example increased number of bits in PBCH. L _(max) X Examplebits 80 4 ā _(A) +8, N_(SSB) ^(QCL) 128 4 ā _(A) +8, N_(SSB) ^(QCL) 1605 ā _(A) +8, ā _(A) +9, N_(SSB) ^(QCL) 256 5 ā _(A) +8, ā _(A) +9,N_(SSB) ^(QCL) 320 6 ā _(A) +8, ā _(A) +9, ā _(A) +10, N_(SSB) ^(QCL)512 6 ā _(A) +8, ā _(A) +9, ā _(A) +10, N_(SSB) ^(QCL)

In one example, ā_(Ā+5) , ā_(Ā+6) , and ā_(Ā+7) are 6th, 5th, and 4thLSB of candidate SSB index, respectively, and ā_(Ā+8) is the 7th bit ofcandidate SSB index.

In another example, ā_(Ā+5) , ā_(Ā+6) , ā_(Ā+7) , and ā_(Ā+8) are 7th,6th, 5th, and 4th LSB of candidate SSB index, respectively.

In yet another example, ā_(Ā+5) , ā_(Ā+6) , and ā_(Ā+7) are 6th, 5th,and 4th LSB of candidate SSB index, respectively, and ā_(Ā+8) andā_(Ā+9) are the 7th and 8th bit of candidate SSB index, respectively.

In yet another example, ā_(Ā+5) , ā_(Ā+6) , ā_(Ā+7) , ā_(Ā+8) andā_(Ā+9) are 8th, 7th, 6th, 5th, and 4th LSB of candidate SSB index,respectively.

In yet another example, ā_(Ā+5) , ā_(Ā+6) , and ā_(Ā+7) are 6th, 5th,and 4th LSB of candidate SSB index, respectively, and ā_(Ā+8) , ā_(Ā+9)and ā_(Ā+10) are the 7th, 8th, and 9th bit of candidate index,respectively.

In yet another example, ā_(Ā+5) , ā_(Ā+6) , ā_(Ā+7) , ā_(Ā+8) , ā_(Ā+9), and ā_(Ā+10) are 9th, 8th, 7th, 6th, 5th, and 4th LSB of candidate SSBindex, respectively.

In yet another example, N_(SSB) ^(QCL) is a 3-bit field taking valuesfrom {1, 2, 4, 8, 16, 32, 64}.

In yet another example, N_(SSB) ^(QCL) is a 3-bit field taking valuesfrom {1, 2, 4, 8, 16, 32, 64, “not applicable”}, wherein the numericalvalues are applicable to channel occupancy with channel sensing (e.g.,listen before talk (LBT)), and the non-numerical values are applicableto channel occupancy without channel sensing (e.g., LBT).

In example, X can be rounded up to the nearest integer as an integermultiple of 8, to make the total number bits generated by the physicallayer an octet, and bits not carrying information are reserved.

In another embodiment, for the higher carrier frequency range consideredin this disclosure, the number of bits in the PBCH payload provided byhigher layer maintains the same as NR Rel-15 and Rel-16, and the numberof bits in the PBCH payload generated by the physical layer alsomaintains the same as NR Rel-15 and Rel-16, but some of the bitsgenerated by the physical layer can be reinterpreted.

In one example, the burst of SS/PBCH blocks within a periodicallytransmitted period is restricted to be confined within the first halfframe in a frame, such that there is no need for indicating the halfframe timing. In this example, the bit ā_(Ā+4) can be used for otherpurpose, wherein ā_(Ā+4) was used for indicating half frame in Rel-15and Rel-16. For one instance, the bit ā_(Ā+4) can be used to indicatethe 7th bit of candidate SSB index, if the number of candidate SS/PBCHblocks is greater than 64. For another instance, the bit ā_(Ā+4) can beused, potentially combined with other bits in PBCH payload, to indicatethe QCL parameter N_(SSB) ^(QCL). Examples are shown in TABLE 5A.

In another example, the burst of SS/PBCH blocks within a periodicallytransmitted period is restricted to be confined within the second halfframe in a frame, such that there is no need for indicating the halfframe timing. In this example, the bit ā_(Ā+4) can be used for otherpurpose. For one instance, the bit ā_(Ā+4) can be used to indicate the7th LSB of candidate SSB index, if the number of candidate SS/PBCHblocks is greater than 64. For another instance, the bit ā_(Ā+4) can beused, potentially combined with other bits in PBCH payload, to indicatethe QCL parameter N_(SSB) ^(QCL). Examples are shown in TABLE 5A.

TABLE 5A Example PHY bits for higher carrier frequency range Bit Example1 Example 2 ā _(A) 4th LSB of SFN 4th LSB of SFN ā _(A) +1 3rd LSB ofSFN 3rd LSB of SFN ā _(A) +2 2nd LSB of SFN 2nd LSB of SFN ā _(A) +3 1stLSB of SFN 1st LSB of SFN ā _(A) +4 7th LSB of candidate SSB indexIndicating N_(SSB) ^(QCL) ā _(A) +5 6th LSB of candidate SSB index 6thLSB of candidate SSB index ā _(A) +6 5th LSB of candidate SSB index 5thLSB of candidate SSB index ā _(A) +7 4th LSB of candidate SSB index 4thLSB of candidate SSB index

For yet another example, if the maximum number of candidate SS/PBCHblock locations within a half frame is larger than 64 (e.g., L_(max)>64), and more DM-RS sequences (e.g., more than 8 per cell) aresupported, more LSBs of the candidate SS/PBCH block index can be carriedby the DM-RS sequences, and the bits generated by physical layer canhave different interpretation. Examples are shown in TABLE 5B.

TABLE 5B Example PHY bits for higher carrier frequency range Example 1Example 2 Example 3 (16 DM-RS (32 DM-RS (64 DM-RS Bit sequences percell) sequences per cell) sequences per cell) ā _(A) 4th LSB of SFN 4thLSB of SFN 4th LSB of SFN ā _(A) +1 3rd LSB of SFN 3rd LSB of SFN 3rdLSB of SFN ā _(A) +2 2nd LSB of SFN 2nd LSB of SFN 2nd LSB of SFN ā _(A)+3 1st LSB of SFN 1st LSB of SFN 1st LSB of SFN ā _(A) +4 Half frame bitHalf frame bit Half frame bit ā _(A) +5 7th LSB of 8th LSB of 9th LSB ofcandidate SSB index candidate SSB index candidate SSB index ā _(A) +66th LSB of 7th LSB of 8th LSB of candidate SSB index candidate SSB indexcandidate SSB index ā _(A) +7 5th LSB of 6th LSB of 7th LSB of candidateSSB index candidate SSB index candidate SSB index

In yet another embodiment, for the higher carrier frequency rangeconsidered in this disclosure, the number of bits in the PBCH payloadprovided by higher layer maintains the same as NR Rel-15 and Rel-16, andthe number of bits in the PBCH payload generated by the physical layeralso maintains the same as NR Rel-15 and Rel-16, but the fields providedby higher layer and bits generated by the physical layer can havedifferent size and meaning.

In one example, the MIB in the PBCH payload contains 7 MSBs of SFN(e.g., the 4th LSB of SFN is also contained in MIB), and one bit (e.g.,a field with 1 bit or 1 bit from a field with multiple bits in Rel-15and Rel-16) is removed from MIB.

In one example, the one bit removed from MIB can be the field ofsubCarrierSpacingCommon, and the corresponding example MIB is shown inTABLE 6A.

TABLE 6A Example MIB for higher carrier frequency range Number FieldValue of bits systemFrameNumber- BIT STRING (SIZE (7)) 7 newssb-SubcarrierOffset INTEGER (0..15) 4 dmrs-TypeA-Position ENUMERATED{pos2, pos3} 1 pdcch-ConfigSIB1 PDCCH-ConfigSIB1 8 cellBarred ENUMERATED{barred, 1 notBarred} intraFreqReselection ENUMERATED {allowed, 1notAllowed} spare BIT STRING (SIZE (1)) 1

In another example, the one bit removed from MIB can be 1 bit from thefield of pdcch-ConfigSIB1 (e.g., from 8 bits to 7 bits), and thecorresponding example MIB is shown in TABLE 6B.

TABLE 6B Example MIB for higher carrier frequency range Number FieldValue of bits systemFrameNumber-new BIT STRING (SIZE (7)) 7subCarrierSpacingCommon- ENUMERATED {scs1-new, 1 new scs2-new}ssb-SubcarrierOffset INTEGER (0..15) 4 dmrs-TypeA-Position ENUMERATED{pos2, pos3} 1 pdcch-ConfigSIB1-new PDCCH-ConfigSIB1-new 7 cellBarredENUMERATED {barred, 1 notBarred} intraFreqReselection ENUMERATED{allowed, 1 notAllowed} spare BIT STRING (SIZE(1)) 1

In yet another example, the one bit removed from MIB can be the field ofspare, and the corresponding example MIB is shown in TABLE 6C.

TABLE 6C Example MIB for higher carrier frequency range Number FieldValue of bits systemFrameNumber-new BIT STRING (SIZE (7)) 7subCarrierSpacingCommon- ENUMERATED {scs1-new, 1 new scs2-new}ssb-SubcarrierOffset INTEGER (0..15) 4 dmrs-TypeA-Position ENUMERATED{pos2, pos3} 1 pdcch-ConfigSIB1 PDCCH-ConfigSIB1 8 cellBarred ENUMERATED{barred, 1 notBarred} intraFreqReselection ENUMERATED {allowed, 1notAllowed}

In yet another example, the fields in the MIB can maintain their nameand bitwidth, but the fields can be re-interpreted for indicating otherinformation, as described in examples of this disclosure. For thisexample, some of the PHY bits can be re-interpreted, and examples areshown in TABLE 7.

TABLE 7 Example PHY bits for higher carrier frequency range Bit Example1 Example 2 ā _(A) 7th LSB of candidate 3rd LSB of SFN SSB index ā _(A)+1 3rd LSB of SFN 2nd LSB of SFN ā _(A) +2 2nd LSB of SFN 1st LSB of SFNā _(A) +3 1st LSB of SFN Half frame bit ā _(A) +4 Half frame bit 7th LSBof candidate SSB index ā _(A) +5 6th LSB of 6th LSB of candidate SSBindex candidate SSB index ā _(A) +6 5th LSB of 5th LSB of candidate SSBindex candidate SSB index ā _(A) +7 4th LSB of 4th LSB of candidate SSBindex candidate SSB index

In one embodiment, for the higher carrier frequency range considered inthis disclosure, there is an indication of a parameter for QCLassumption in PBCH payload, such that a UE determines SS/PBCH blocks areQCLed within or across transmission windows for SS/PBCH blocks if thevalue of (ι mod N_(SSB) ^(QCL)) for the corresponding SS/PBCH blocks isthe same, wherein ι is the candidate SS/PBCH block index, and N_(SSB)^(QCL) is the indicated parameter for QCL assumption.

In one example, for the higher carrier frequency range considered inthis disclosure, N_(SSB) ^(QCL) is taking values from {1, 4, 16, 64},and 2 bits in PBCH payload are used for the indication of N_(SSB)^(QCL).

In another example, for the higher carrier frequency range considered inthis disclosure, N_(SSB) ^(QCL) is taking values from {1, 2, 4, 8, 16,32, 64}, and 3 bits in PBCH payload are used for the indication ofN_(SSB) ^(QCL).

In yet another example, for the higher carrier frequency rangeconsidered in this disclosure, N_(SSB) ^(QCL) is taking values from {1,2, 4, 8, 16, 32, 48, 64}, and 3 bits in PBCH payload are used for theindication of N_(SSB) ^(QCL).

In yet another example, for the higher carrier frequency rangeconsidered in this disclosure, N_(SSB) ^(QCL) is taking values from {1,2, 4, 8, 16, 24, 32, 40, 48, 56, 64}, and 4 bits in PBCH payload areused for the indication of N_(SSB) ^(QCL).

One example for using 2 bits in PBCH payload to indicate N_(SSB) ^(QCL)can be 2 LSBs of ssb-SubcarrierOffset.

Another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset and 1 bitof subCarrierSpacingCommon.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 bit of spare and 1 bit ofsubCarrierSpacingCommon.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 bit of spare and 1 LSB ofssb-SubcarrierOffset.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 2 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1.

One example for using 3 bits in PBCH payload to indicate N_(SSB) ^(QCL)can be the 3 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

Another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the 3 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the 3 LSBs of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the 3 MSBs of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the 3 MSBs of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the 3 LSBs of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset and 1bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of ssb-SubcarrierOffset and 1bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset and 1bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of ssb-SubcarrierOffset and 1bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 2 MSBs of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 2 LSBs of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 1 LSB of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 1 MSB of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of spare.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of subCarrierSpacingCommon.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 1 LSB of searchSpaceZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 1 MSB of searchSpaceZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB ofsearchSpaceZero in pdcch-ConfigSIB1, and 1 MSB of controlResourceSetZeroin pdcch-ConfigSIB1.

Yet another example for using 3 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB ofsearchSpaceZero in pdcch-ConfigSIB1, and 1 LSB of controlResourceSetZeroin pdcch-ConfigSIB1.

One example for using 4 bits in PBCH payload to indicate N_(SSB) ^(QCL)can be the combination of 3 LSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of ssb-SubcarrierOffset and 1bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of ssb-SubcarrierOffset and 1bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of ssb-SubcarrierOffset and 1bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of ssb-SubcarrierOffset and 1bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 2 MSBs of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 2 LSBs of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 3 MSBs of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 3 LSBs of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1 and 3 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1 and 3 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 MSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 3 LSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 1 LSB of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of controlResourceSetZero inpdcch-ConfigSIB1 and 2 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1 and 3 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1 and 3 LSBs of ssb-SubcarrierOffset.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of controlResourceSetZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of controlResourceSetZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1, 1 bit of subCarrierSpacingCommon, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof spare, and 1 LSB of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof spare, and 1 MSB of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 2 LSBs of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 2 MSBs of searchSpaceZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof spare, and 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof spare, and 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, and 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1, 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1, 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 MSB of searchSpaceZero inpdcch-ConfigSIB1, 2 MSBs of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of searchSpaceZero inpdcch-ConfigSIB1, 2 LSBs of controlResourceSetZero in pdcch-ConfigSIB1,and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof subCarrierSpacingCommon, and 1 LSB of searchSpaceZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof subCarrierSpacingCommon, and 1 MSB of searchSpaceZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 2 LSBs of searchSpaceZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 2 MSBs of searchSpaceZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofsubCarrierSpacingCommon, and 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof subCarrierSpacingCommon, and 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 2 LSBs of ssb-SubcarrierOffset, 1 bitof subCarrierSpacingCommon, and 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB ofsearchSpaceZero in pdcch-ConfigSIB1, and 2 MSBs ofcontrolResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB ofsearchSpaceZero in pdcch-ConfigSIB1, and 2 LSBs ofcontrolResourceSetZero in pdcch-ConfigSIB1.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 bit of spare, 1 LSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 LSB of controlResourceSetZero inpdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 bit of spare, 1 MSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 MSB of controlResourceSetZero inpdcch-ConfigSIB1, and 1 bit of subCarrierSpacingCommon.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, 1 LSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit ofspare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 bit ofspare, 1 MSB of controlResourceSetZero in pdcch-ConfigSIB1, and 1 bit ofspare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 LSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 bit of spare, and 1 bit of spare.

Yet another example for using 4 bits in PBCH payload to indicate N_(SSB)^(QCL) can be the combination of 1 LSB of ssb-SubcarrierOffset, 1 MSB ofsearchSpaceZero in pdcch-ConfigSIB1, 1 bit of spare, and 1 bit of spare.

In another embodiment, for the higher carrier frequency range consideredin this disclosure, N_(SSB) ^(QCL) is indicated in SIB (e.g., SIB1). Inone further example, N_(SSB) ^(QCL) is indicated in both PBCH payloadand SIB, wherein the value for N_(SSB) ^(QCL) in PBCH is a subset of thevalue for N_(SSB) ^(QCL) in SIB. For example, the bitwidth of thefield(s) for indicating N_(SSB) ^(QCL) in PBCH is smaller than thebitwidth of the field for indicating N_(SSB) ^(QCL) in SIB. The examplevalue of N_(SSB) ^(QCL) indicated in SIB can refer to an example valueof N_(SSB) ^(QCL) indicated in PBCH payload.

In one embodiment, for the higher carrier frequency range considered inthis disclosure, there is an indication, in PBCH payload, on whether thefrequency layer, where the corresponding SS/PBCH block is located,operates with shared spectrum channel access or not (e.g., whether ornot a LBT procedure is needed when initializing a channel occupancy).For example, as illustrated in FIG. 6 , a first band can be operatedwith shared spectrum channel access (e.g., requiring LBT procedure wheninitializing a channel occupancy), and a second band can be operatedwithout shared spectrum channel access (e.g., not requiring LBTprocedure when initializing a channel occupancy), wherein the first bandand the second band overlap in frequency domain.

If an SS/PBCH block is located on the overlapped bandwidth, then anindication in PBCH payload can help the UE to distinguish whether thecorresponding SS/PBCH block is operated with shared spectrum channelaccess or not. For another example, one band can be operated with sharedspectrum channel access in a first geography region (e.g., requiring LBTprocedure when initializing a channel occupancy), and can be operatedwithout shared spectrum channel access in a second geography region(e.g., not requiring LBT procedure when initializing a channeloccupancy), then an indication in PBCH payload can help the UE todistinguish whether the corresponding SS/PBCH block is operated withshared spectrum channel access or not.

FIG. 6 illustrates an example overlapping band 600 with and withoutshared spectrum channel access according to embodiments of the presentdisclosure. An embodiment of the overlapping band 600 shown in FIG. 6 isfor illustration only.

In one embodiment, based on this indication, a UE can interpret at leastpart of the PBCH content differently for operation with shared spectrumchannel access and operation without shared spectrum channel access. Anexample UE procedure for determining the payload of PBCH based on theindication of operation with shared spectrum channel access or not isshown in FIG. 7 .

FIG. 7 illustrates a flowchart of a method 700 for an indication ofoperation with shared spectrum channel access or not according toembodiments of the present disclosure. An embodiment of the method 700shown in FIG. 7 is for illustration only. One or more of the componentsillustrated in FIG. 7 can be implemented in specialized circuitryconfigured to perform the noted functions or one or more of thecomponents can be implemented by one or more processors executinginstructions to perform the noted functions.

As illustrated in FIG. 7 , the method 700 begins at step 702. In step702, a UE (e.g., 111-116 as illustrated in FIG. 1 ) decode payload ofPBCH. Subsequently, the UE in step 704 determines in indication onoperation with shared spectrum channel access or not. Next, the UE instep 706 determines whether a shared spectrum channel access isachieved. In step 706, if yes, the UE in step 708 interprets at leastpart of the payload of PBCH in a first way. In step 706, if no, the UEin step 710 interprets at least part of the payload of PBCH in a secondway.

In one example, the indication of operation with shared spectrum channelaccess or not can be with 1 bit in the payload of PBCH, wherein the1-bit indication can be a re-interpretation of one bit in the payload ofPBCH.

For a first example, the 1-bit indication can re-interpret 1 bit ofssb-SubcarrierOffset, e.g., the 1 LSB or MSB.

For a second example, the 1-bit indication can re-interpret 1 bit ofcontrolResourceSetZero in pdcch-ConfigSIB1, e.g., the 1 LSB or MSB.

For a third example, the 1-bit indication can re-interpret 1 bit ofsearchSpaceZero in pdcch-ConfigSIB1, e.g., the 1 LSB or MSB.

For a fourth example, the 1-bit indication can re-interpret the 1 bit ofsubCarrierSpacingCommon.

For a fifth example, the 1-bit indication can re-interpret the 1 bit ofspare.

For a sixth example, the 1-bit indication can re-interpret the 1 bit ofā_(Ā+4) .

For a seventh example, the 1-bit indication can re-interpret the 1 bitof ā_(Ā).

In another example, the indication of operation with shared spectrumchannel access or not can be using the non-used combination of fields inthe payload of PBCH.

For example, when cellBarred is provided as “notBarred,” a UE determinesthe frequency layer operates with shared spectrum channel access ifintraFreqReselection is provided as “allowed”; and the UE determines thefrequency layer operates without shared spectrum channel access ifintraFreqReselection is provided as “notAllowed.”

In another example, when cellBarred is provided as “notBarred,” a UEdetermines the frequency layer operates without shared spectrum channelaccess if intraFreqReselection is provided as “allowed”; and the UEdetermines the frequency layer operates with shared spectrum channelaccess if intraFreqReselection is provided as “notAllowed.”

In yet another example, the indication of operation with shared spectrumchannel access or not is jointly coded with the QCL parameter N_(SSB)^(QCL).

For one example, a non-numerical value for the QCL parameter N_(SSB)^(QCL) can be utilized to indicate operation without shared spectrumchannel access. In one instance, N_(SSB) ^(QCL) is a 3-bit field takingvalues from {1, 2, 4, 8, 16, 32, 64, “not applicable”}, wherein thenumerical values indicate channel occupancy with channel sensing (e.g.,LBT), and the non-numerical values indicates channel occupancy withoutchannel sensing (e.g., LBT).

For another example, a value for the QCL parameter N_(SSB) ^(QCL) sameas the maximum number of candidate SS/PBCH blocks can be utilized toindicate operation without shared spectrum channel access.

In another embodiment, there can be an indication on whether thefrequency layer operates with shared spectrum channel access or notusing a RRC parameter. For example, the indication can be in a cellspecific configuration, e.g., SIB1 and/or ServingCellConfigCommon. Foranother example, the indication can be in a UE-specific configuration.

In one embodiment, for the higher carrier frequency range considered inthis disclosure, there can be an indication in MIB on the 4th LSB ofSFN, using 1 bit reinterpreted from Rel-15 or Rel-16.

For a first example, the 1-bit indication can re-interpret 1 bit ofssb-SubcarrierOffset, e.g., the 1 LSB or MSB.

For a second example, the 1-bit indication can re-interpret 1 bit ofcontrolResourceSetZero in pdcch-ConfigSIB1, e.g., the 1 LSB or MSB.

For a third example, the 1-bit indication can re-interpret 1 bit ofsearchSpaceZero in pdcch-ConfigSIB1, e.g., the 1 LSB or MSB.

For a fourth example, the 1-bit indication can re-interpret the 1 bit ofsubCarrierSpacingCommon.

For a fifth example, the 1-bit indication can re-interpret the 1 bit ofspare.

For this embodiment, the indication of ā_(Ā) in the PHY bits, which isthe 4th LSB of SFN in Rel-15 and Rel-16, can be re-interpreted, andexamples are shown in TABLE 7.

In one embodiment, for the higher carrier frequency range considered inthis disclosure, the quantity k_(SSB) is the subcarrier offset fromsubcarrier 0 in common resource block N_(CRB) ^(SSB) to subcarrier 0 ofthe SS/PBCH block, or for providing information on another cell-definingSS/PBCH block, based on a value range.

In one example, for the higher carrier frequency range considered inthis disclosure, the quantity k_(SSB) is expressed in terms of thesubcarrier spacing of CORESET #0. For one example, the subcarrierspacing of CORESET #0 is the same as the subcarrier spacing of theSS/PBCH block. For another example, the subcarrier spacing of CORESET #0is provided by higher layer parameter subCarrierSpacingCommon.

In one example, if the LSB of ssb-SubcarrierOffset is utilized forindicating other information (e.g., QCL parameter N_(SSB) ^(QCL) oroperation with shared spectrum channel access or not, or 4th LSB of SFN,or etc.), as described in an example of this disclosure, then k_(SSB)(or equivalently the 4 LSBs of k_(SSB)) is given by the higher-layerparameter ssb-SubcarrierOffset. If k _(SSB)≥12, k _(SSB)=k _(SSB);otherwise, k_(SSB)=2└k _(SSB)/2┘.

In another example, if the 2 LSBs of ssb-SubcarrierOffset is utilizedfor indicating other information (e.g., QCL parameter N_(SSB) ^(QCL) oroperation with shared spectrum channel access or not, or 4th LSB of SFN,or etc.), as described in an example of this disclosure, then k _(SSB)(or equivalently the 4 LSBs of k _(SSB)) is given by the higher-layerparameter ssb-SubcarrierOffset. If k _(SSB)≥12, k _(SSB)=k _(SSB);otherwise, k_(SSB)=4 └k _(SSB)/4┘.

In yet another example, if the 3 LSBs of ssb-SubcarrierOffset isutilized for indicating other information (e.g., QCL parameter N_(SSB)^(QCL), or operation with shared spectrum channel access or not, or 4thLSB of SFN, or etc.), as described in an example of this disclosure,then k _(SSB) (or equivalently the 4 LSBs of k _(SSB)) is given by thehigher-layer parameter ssb-SubcarrierOffset. If k _(SSB)≥12, k_(SSB)=k_(SSB); otherwise, k_(SSB)=8└k _(SSB)/8┘.

In another example, if the field ssb-SubcarrierOffset is utilized forindicating other information (e.g., QCL parameter N_(SSB) ^(QCL), oroperation with shared spectrum channel access or not, or 4th LSB of SFN,or etc.), as described in an example of this disclosure, then k _(SSB)(or equivalently the 4 LSBs of k _(SSB)) is given by the higher-layerparameter ssb-SubcarrierOffset. If k _(SSB)≥12, k_(SSB)=k _(SSB);otherwise, k_(SSB)=0.

In one embodiment, for the higher carrier frequency range considered inthis disclosure, the interleaving PBCH payload can have correspondingchanges when the bits in PBCH payloads are re-interpreted.

In one example, the interleaving of bits generated by physical layer inPBCH payload can be according to the following. For one example, thisexample can be at least applicable to Example 1 in TABLE 5A.

TABLE 8 The interleaving of bits generated by physical layer in PBCHpayload Let A = Ā + 8; j_(SFN) = 0; j_(SSB) = 10; j_(other) = 14; for i= 0 to A − 1    if ā_(i) is an SFN bit      a_(G(j) _(SFN) ₎ = ā_(i);     j_(SFN) = j_(SFN) + 1;  clscif ā_(i) is a candidate SS/PBCH blockindex bit     a_(G(j) _(SSB) ₎ = ā_(i);   j_(SSB) = j_(SSB) + 1;  else     a_(G(j) _(other) ₎ = ā_(i);   j_(other) = j_(other) + 1;  end ifend for

For another example, the interleaving of bits generated by physicallayer in PBCH payload can be according to the following. For oneexample, this example can be at least applicable to Example 2 in TABLE5A.

TABLE 9 The interleaving of bits generated by physical layer in PBCHpayload Let A = Ā + 8; j_(SFN) = 0; j_(QCL) = 10; j_(SSB) = 11;j_(other) = 14; for i = 0 to A − 1    if ā_(i) is an SFN bit     a_(G(j) _(SFN) ₎ = ā_(i);      j_(SFN) = j_(SFN) + 1;  elseif ā_(i)is a bit for indicating N_(SSB) ^(QCL)     a_(G(j) _(QCL) ₎ = ā_(i); clscif ā_(i) is a candidate SS/PBCH block index bit     a_(G(j) _(SSB)₎ = ā_(i);   j_(SSB) = j_(SSB) + 1;  else      a_(G(j) _(other) ₎ =ā_(i);   j_(other) = j_(other) + 1;  end if end for

For yet another example, the interleaving of bits generated by physicallayer in PBCH payload can be according to the following. For oneexample, this example can be at least applicable to Example 1 in TABLE7.

TABLE 10 The interleaving of bits generated by physical layer in PBCHpayload Let A = Ā + 8; j_(SFN) = 1; j_(HRF) = 10; j_(SSB) = 0; j_(other)= 14; for i = 0 to A − 1    if α _(i) is an SFN bit     α_(G (j) _(SFN)₎ = α _(i);     j_(SFN) = j_(SFN) + 1;    elseif α _(i) is the halfradio frame bit     α_(G (j) _(HRF) ₎ = α _(i);   elseif α _(i) is acandidate SS/PBCH block index bit     α_(G (j) _(SSB) ₎ = α _(i);   if i= Ā     j_(SSB) = j_(SSB) + 11;   else    j_(SSB) = j_(SSB) + 1;   endif   else     α_(G) (_(j) _(other) ) α _(i);   j_(other) = j_(other) +1;  end if  end for

For yet another example, the interleaving of bits generated by physicallayer in PBCH payload can be according to the following. For oneexample, this example can be at least applicable to Example 2 in TABLE7.

TABLE 11 The interleaving of bits generated by physical layer in PBCHpayload Let A = Ā + 8; j_(SFN) = 0; j_(HRF) = 9; j_(SSB) = 10; j_(other)= 14; for i = 0 to A − 1    if α _(i) is an SFN bit      α_(G (j) _(SFN)₎ = α _(i);      j_(SFN) = j_(SFN) + 1;    elseif α _(i) is the halfradio frame bit      α_(G (j) _(HRF) ₎ = α _(i);   elseif α _(i) is acandidate SS/PBCH block index bit     α_(G (j) _(SSB) ₎ = α _(i);   j_(SSB) = j_(SSB) + 1;   else      α_(G (j) _(other) ₎ = α _(i);   j_(other) = j_(other) + 1;   end if  end for

In one embodiment, for the higher carrier frequency range considered inthis disclosure, the scrambling of PBCH payload can have correspondingchanges when the bits in PBCH payloads are re-interpreted.

In one example, for the Example 1 and Example 2 in TABLE 5A, the lengthof the segments of the scrambling sequence (e.g., M) is determined asM=A−6.

In another example, for the Example 1 and Example 2 in TABLE 7, thelength of the segments of the scrambling sequence (e.g., M) isdetermined as M=A−7.

In one embodiment, for the higher carrier frequency range considered inthis disclosure, the number of DM-RS sequences for PBCH per cell can beincreased (e.g., larger than 8).

In one example, the generation of DM-RS sequences for PBCH is based onthe pseudo-random sequence c(i) with changes to the initial condition ofthe generator to support larger number of sequences per cell, whereinthe initial condition is according to: c_(init)=c₁(ι _(SSB)+1)(└N_(ID)^(cell)/4┘+1)+c₂(ι _(SSB)+1)+(N_(ID) ^(cell) mod 4), where ι _(SSB) isLSBs of candidate SS/PBCH block index with 0≤ι _(SSB)≤N _(DM-RS)^(PBCH)−1, and N _(DM-RS) ^(PBCH) is the number of DM-RS sequences percell.

In one example, N _(DM-RS) ^(PBCH)=16 such that ι _(SSB) is the 4 LSBsof candidate SS/PBCH block index, and c₁=2¹¹, c₂=2⁶.

In another example, N _(DM-RS) ^(PBCH)=16 such that ι _(SSB) is the 4LSBs of candidate SS/PBCH block index, and c₁=2⁰, c₂=2¹⁴.

In yet another example, N _(DM-RS) ^(PBCH)=16 such that ι _(SSB) is the4 LSBs of candidate SS/PBCH block index, and c₁=2¹⁶, c₂=2³.

In yet another example, N _(DM-RS) ^(PBCH)=32 such that ι _(SSB) is the5 LSBs of candidate SS/PBCH block index, and c₁=2¹¹, c₂=2⁶.

In yet another example, N _(DM-RS) ^(PBCH)=32 such that ι _(SSB) is the5 LSBs of candidate SS/PBCH block index, and c₁=2¹⁶, c₂=2³.

In yet another example, N _(DM-RS) ^(PBCH)=32 such that ι _(SSB) is the5 LSBs of candidate SS/PBCH block index, and c₁=2¹², c₂=2⁴.

In yet another example, N _(DM-RS) ^(PBCH)=64 such that ι _(SSB) is the6 LSBs of candidate SS/PBCH block index, and c₁=2¹¹, c₂=2⁶.

In yet another example, N _(DM-RS) ^(PBCH)=64 such that ι _(SSB) is the6 LSBs of candidate SS/PBCH block index, and c₁=2¹⁶, c₂=2³.

The present disclosure focuses on the CORESET #0 configuration. Inparticular, the embodiments of this disclosure are at least applicableto operation with shared spectrum channel access. The embodiments on theconfiguration design are based on the multiplexing pattern betweenSS/PBCH block and CORESET #0. The details of this disclosure include:(1) CORESET #0 configuration for Pattern 1; (2) CORESET #0 configurationfor Pattern 2; and (3) CORESET #0 configuration for Pattern 3.

In NR Rel-15 and Rel-16, MIB in the payload of PBCH includes a fieldcontaining the configuration of CORESET for monitoring Type0-PDCCHcommon search space (CSS), which is denoted as CORESET #0. In NR Rel-15and Rel-16, the multiplexing pattern between SS/PBCH block (SSB) andCORESET #0, the BW of CORESET #0, the number of symbols for CORESET #0,and the RB offset from a smallest RB index of the CORESET forType0-PDCCH CSS set to a smallest RB index of the common RB overlappingwith a first RB of the SS/PBCH block, are jointly coded using 4 bits,i.e., the field of controlResourceSetZero in pdcch-ConfigSIB1.

In NR Rel-15 and Rel-16, three multiplexing patterns between SS/PBCHblock and CORESET #0 have been supported. In Pattern 1, the bandwidth ofSS/PBCH block and the bandwidth of CORESET #0 overlap, and the instanceof SS/PBCH block and instance of CORESET #0 do not take place at thesame time; in Pattern 2, the bandwidth of SS/PBCH block and thebandwidth of CORESET #0 do not overlap, and the instance of SS/PBCHblock and instance of CORESET #0 do not take place at the same time; inPattern 3, the bandwidth of SS/PBCH block and the bandwidth of CORESET#0 do not overlap, and the instance of SS/PBCH block and instance ofCORESET #0 take place at the same time. An illustration of themultiplexing patterns is shown in FIG. 8 .

FIG. 8 illustrates example multiplexing patterns 800 between SSB andCORESET #0 according to embodiments of the present disclosure. Anembodiment of the multiplexing patterns 800 shown in FIG. 8 is forillustration only.

For a new carrier frequency range between 52.6 GHz and 71 GHz, a newnumerology at least with a larger subcarrier spacing could be supported,to accommodate the larger phase noise and larger carrier bandwidth. Whena new numerology (e.g., including a new subcarrier spacing) is supportedin NR, the CORESET #0 configuration can be enhanced in order to supportsuch new numerology. This disclosure specifies the details of CORESET #0configuration for higher frequency range, wherein the higher frequencyrange at least includes the carrier frequency range between 52.6 GHz and71 GHz, and can be applicable to both licensed (e.g., operated withoutshared spectrum channel access) and unlicensed bands (e.g., operatedwith shared spectrum channel access) in the frequency range.

In the present disclosure, CORESET #0 refers to the control resource set(CORESET) of the Type0-PDCCH common search space set.

In one embodiment, a common configuration table can be utilized for bothoperations with and without shared spectrum channel access, for a givensupported combination of SCS of SS/PBCH block and CORESET #0. For thisexample, an example in this disclosure can be utilized for bothoperations with and without shared spectrum channel access, for a givensupported combination of SCS of SS/PBCH block and CORESET #0.

In another embodiment, a separate configuration table can be utilizedfor operation with or without shared spectrum channel access, for agiven supported combination of SCS of SS/PBCH block and CORESET #0. Forthis example, one example in this disclosure can be utilized foroperation with shared spectrum channel access, and another example inthis disclosure can be utilized for operation without shared spectrumchannel access, for a given supported combination of SCS of SS/PBCHblock and CORESET #0.

In one embodiment, there can be a large granularity of channel rasterinterval (e.g., as large as one nominal channel BW) and a largegranularity of synchronization raster interval (e.g., e.g., as large asone nominal channel BW), such that there is only one synchronizationraster entry within a nominal channel BW. For instance, thechannelization and synchronization raster design can be applicable tooperation with shared spectrum channel access, and the example CORESET#0 configuration in this disclosure is applicable to operation withshared spectrum channel access.

In one example, within a nominal channel BW (e.g., BW can be 2.16 GHz),there is one synchronization raster entry within a nominal channel, andone channel raster entry within the nominal channel. An illustration ofthis example is shown in FIG. 8 .

FIG. 9 illustrates an example second type of channelization andsynchronization raster 900 according to embodiments of the presentdisclosure. An embodiment of the second type of channelization andsynchronization raster 900 shown in FIG. 9 is for illustration only.

In one embodiment, a supported SCS for a nominal channel can be 960 kHz,and the corresponding available number of RBs (e.g., not including theguard band) can be N_(RB) ⁹⁶⁰. For example, N_(RB) ⁹⁶⁰=178 for nominalBW around 2 GHz. For another example, N_(RB) ⁹⁶⁰=180 for nominal BWaround 2 GHz.

In another embodiment, a supported SCS for a nominal channel can be 480kHz, and the corresponding available number of RBs (e.g., not includingthe guard band) can be N_(RB) ⁹⁶⁰. For example, N_(RB) ⁹⁶⁰=275 fornominal BW around 2 GHz, if the maximum FFT size is considered as 4096.

In yet another embodiment, as least one of Pattern 2 and/or Pattern 3,in addition to Pattern 1, can be supported as the multiplexing patternbetween SS/PBCH block and Type0-PDCCH within the CORESET #0. Forexample, both Pattern 2 and Pattern 3 are supported, in addition toPattern 1.

In one embodiment, at least Pattern 1 can be supported and configured asthe multiplexing pattern between SS/PBCH block and associated CORESET#0.

In one example, Pattern 1 can be configured for all the supportedcombinations of SCSs of SS/PBCH block and CORESET #0.

In another embodiment, the BW of CORESET #0 in term of RBs and withrespect to the SCS of Type0-PDCCH within the CORESET #0 (e.g., denotedas N_(RB) ^(CORESET #0)) can be configured to be no smaller than theminimum requirement from regulation for operation with shared spectrumchannel access.

For one example, the at least one configurable N_(RB) ^(CORESET #0) isquantized to an integer as a multiple of six, e.g., N_(RB)^(CORESET #0)≥6·┌(BW_(carrier)·ρ)/(SCS_(CORESET)·12·6)┐, wherein ρ isthe required ratio of bandwidth occupancy in regulation, and BW carrieris the nominal carrier bandwidth. For one example, at least oneconfigurable N_(RB) ^(CORESET #0)≥132 RB, for SCS_(CORESET)=960 kHz,BW_(carrier)=2 GHz, and ρ=70%. For another example, at least oneconfigurable N_(RB) ^(CORESET #0≥)264 RB, for SCS_(CORESET)=480 kHz,BW_(carrier)=2 GHz, and ρ=70%.

For another example, the at least one configurable N_(RB) ^(CORESET #0)is quantized to an integer as a multiple of twelve, e.g., N_(RB)^(CORESET #0)≥12·┌(BW_(carrier)·ρ)/(SCS_(CORESET)·12·12)┐, wherein ρ isthe required ratio of bandwidth occupancy in regulation, andBW_(carrier) is the nominal carrier bandwidth. For one example, at leastone configurable N_(RB) ^(CORESET #0)≥132 RB, for SCS_(CORESET)=960 kHz,BW_(carrier)=2 GHz, and ρ=70%. For another example, at least oneconfigurable N_(RB) ^(CORESET #0)≥264 RB, for SCS_(CORESET)=480 kHz,BW_(carrier)=2 GHz, and ρ=70%.

In another embodiment, the BW of CORESET #0 in term of RBs and withrespect to the SCS of Type0-PDCCH within the CORESET #0 (e.g., denotedas N_(RB) ^(CORESET #0)) can be configured to be no larger than themaximum number of RBs from channelization of all supported carriersoverlapping with a nominal channel.

For one example, the at least one configurable N_(RB) ^(CORESET #0) isquantized to an integer as a multiple of six. For example, N_(RB)^(CORESET #0)≤6·└N_(RB) ⁹⁶⁰/6┘ for SCS_(CORESET)=960 kHz, e.g., N_(RB)^(CORESET #0)≤174 RB for SCS_(CORESET)=960 kHz. For another example,N_(RB) ^(CORESET #0)≤6. └N_(RB) ⁴⁸⁰/6┘ for SCS_(CORESET)=480 kHz, e.g.,N_(RB) ^(CORESET #0)≤270 RB for SCS_(CORESET)=480 kHz.

For another example, the at least one configurable N_(RB) ^(CORESET #0)is quantized to an integer as a multiple of twelve. For example, N_(RB)^(CORESET #0)≤12·└N_(RB) ⁹⁶⁰/12┘ or SCS_(CORESET)=960 kHz, e.g., N_(RB)^(CORESET #0)≤168 RB for SCS=960 kHz. For another example, N_(RB)^(CORESET #0)=12·└N_(RB) ⁴⁸⁰/12┘ for SCS_(CORESET)=480 kHz, e.g., N_(RB)^(CORESET #0)≤264 RB for SCS_(CORESET)=480 kHz.

In one example, for Pattern 1, the BW of CORESET #0 in term of RBs andwith respect to the SCS of Type0-PDCCH within the CORESET #0 (e.g.,denoted as N_(RB) ^(CORESET #0)) is fixed as the maximum number of RBsfrom channelization of all supported carriers overlapping with a nominalchannel. In one instance, N_(RB) ^(CORESET #0) is determined as 174 (or168) RBs when the SCS of Type0-PDCCH within the CORESET #0 is 960 kHzand configured with Pattern 1. In another instance, N_(RB) ^(CORESET #0)is determined as 270 (or 264) RBs when the SCS of Type0-PDCCH within theCORESET #0 is 480 kHz and configured with Pattern 1.

In another example, for Pattern 1, the BW of CORESET #0 in term of RBsand with respect to the SCS of Type0-PDCCH within the CORESET #0 (e.g.,denoted as N_(RB) ^(CORESET #0)) is fixed as the minimum requirementfrom regulation for operation with shared spectrum channel access. Inone instance, N_(RB) ^(CORESET #0) is determined as 132 RBs when the SCSof Type0-PDCCH within the CORESET #0 is 960 kHz and configured withPattern 1. In another instance, N_(RB) ^(CORESET #0) is determined as264 RBs when the SCS of Type0-PDCCH within the CORESET #0 is 480 kHz andconfigured with Pattern 1.

In yet another example, for Pattern 1, the BW of CORESET #0 in term ofRBs and with respect to the SCS of Type0-PDCCH within the CORESET #0(e.g., denoted as N_(RB) ^(CORESET #0)) can be at least configurable asat least one integer between maximum number of RBs from channelizationof all supported carriers overlapping with a nominal channel and theminimum requirement from regulation for operation with shared spectrumchannel access. In one instance, N_(RB) ^(CORESET #0) is configurablefrom a set of integers, wherein the integers are chosen from 132 to 174(or 168) RBs when the SCS of Type0-PDCCH within the CORESET #0 is 960kHz and configured with Pattern 1. In another instance, N_(RB)^(CORESET #0) is configurable from a set of integers, wherein theintegers are chosen from 264 to 270 RBs when the SCS of Type0-PDCCHwithin the CORESET #0 is 480 kHz and configured with Pattern 1.

In yet another example, for Pattern 1, the BW of CORESET #0 in term ofRBs and with respect to the SCS of Type0-PDCCH within the CORESET #0(e.g., denoted as N_(RB) ^(CORESET #0)) can be at least configurable as12·n, where n is an integer such that 12·n is no larger than the maximumnumber of RBs per carrier. In one instance, N_(RB) ^(CORESET #0) isconfigurable from a set of or a subset of {24, 48, 96, BW_(max)} whenthe SCS of Type0-PDCCH within the CORESET #0 is 960 kHz, whereinBW_(max) can be one integer from 132 to 174 (for example 174 or 168 or132). In another instance, N_(RB) ^(CORESET #0) is configurable from aset of or a subset of {24, 48, 96, 192, BW_(max)} when both the SCS ofSS/PBCH block and the SCS of Type0-PDCCH within the CORESET #0 are 480kHz, wherein BW_(max) can be one integer from 264 to 270 (for example264 or 270). In yet another instance, N_(RB) ^(CORESET #0) isconfigurable from a set of or a subset of {48, 96, 192, BW_(max)} whenthe SCS of SS/PBCH block is 960 kHz and the SCS of Type0-PDCCH withinthe CORESET #0 is 480 kHz, wherein BW_(max) can be one integer from 264to 270 (for example 264 or 270).

FIG. 10 illustrates an example CORESET #0 BW 1000 for pattern 1according to embodiments of the present disclosure. An embodiment of theCORESET #0 BW 1000 shown in FIG. 10 is for illustration only.

In another embodiment, an RB offset from a smallest RB index of theCORESET for Type0-PDCCH CSS set to a smallest RB index of the common RBoverlapping with a first RB of the SS/PBCH block can be associated witha supported CORESET #0 BW.

In one example, the RB offset from a smallest RB index of the CORESETfor Type0-PDCCH CSS set to a smallest RB index of the common RBoverlapping with a first RB of the SS/PBCH block can be fixed as 0 RB,for a given supported CORESET #0 BW. In one instance, this example canbe applicable to the case where CORESET #0 BW is not BW_(max).

In another example, the RB offset from a smallest RB index of theCORESET for Type0-PDCCH CSS set to a smallest RB index of the common RBoverlapping with a first RB of the SS/PBCH block can be configurable,for a given supported CORESET #0 BW. In one instance, the RB offset canbe configurable from the set or a subset of {0, 1, 2, 3} if the CORESET#0 BW is BW_(max) and the SCS of Type0-PDCCH within the CORESET #0 issame as the SCS of SS/PBCH block. In another instance, the RB offset canbe configurable from the set or a subset of {0, 2} if the CORESET #0 BWis BW_(max) and the SCS of Type0-PDCCH within the CORESET #0 is largerthan the SCS of SS/PBCH block. In yet another instance, the RB offsetcan be configurable from the set or a subset of {0, 2, 4, 6} if theCORESET #0 BW is BW_(max) and the SCS of Type0-PDCCH within the CORESET#0 is smaller than the SCS of SS/PBCH block.

In yet another embodiment, the number of symbols for CORESET #0 can beconfigurable between 1 and 2, for Pattern 1. In one additional example,the number of symbols for CORESET #0 can be further configurable as 3 ifthe BW of CORESET #0 is 48 RB or smaller. Example configurations forPattern 1 with {SCS_(SSB), SCS_(CORESET)}={960 kHz, 960 kHz} are shownin TABLE 12A, and at least a subset from the table can be supported,wherein BW_(max) can be one integer from 132 to 174 (for example 174 or168 or 132).

TABLE 12A Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {960 kHz, 960 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 1BW_(max) 1 0 1 1 BW_(max) 1 1 2 1 BW_(max) 1 2 3 1 BW_(max) 1 3 4 1BW_(max) 2 0 5 1 BW_(max) 2 1 6 1 BW_(max) 2 2 7 1 BW_(max) 2 3 8 1 92 10 9 1 92 2 0 10 1 48 1 0 11 1 48 2 0 12 1 48 3 0 13 1 24 1 0 14 1 24 2 015 1 24 3 0

Example configurations for Pattern 1 with {SCS_(SSB),SCS_(CORESET)}={480 kHz, 960 kHz} are shown in TABLE 12B, and at least asubset from the table can be supported, wherein BW_(max) can be oneinteger from 132 to 174 (for example 174 or 168 or 132).

TABLE 12B Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {480 kHz, 960 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 1BW_(max) 1 0 1 1 BW_(max) 1 2 2 1 BW_(max) 2 0 3 1 BW_(max) 2 2 4 1 92 10 5 1 92 2 0 6 1 48 1 0 7 1 48 2 0 8 1 48 3 0 9 1 24 1 0 10 1 24 2 0 111 24 3 0

Example configurations for Pattern 1 with {SCS_(SSB),SCS_(CORESET)}={960 kHz, 480 kHz} are shown in TABLE 12C, and at least asubset from the table can be supported, wherein BW_(max) can be 270 or264.

TABLE 12C Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {960 kHz, 480 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 1BW_(max) 1 0 1 1 BW_(max) 1 2 2 1 BW_(max) 1 4 3 1 BW_(max) 1 6 4 1BW_(max) 2 0 5 1 BW_(max) 2 2 6 1 BW_(max) 2 4 7 1 BW_(max) 2 6 8 1 92 10 9 1 92 2 0 10 1 48 1 0 11 1 48 2 0 12 1 48 3 0

In one embodiment, Pattern 2 can be supported and configured as themultiplexing pattern between SS/PBCH block and CORESET #0, at least forsome of the combinations of SCSs of SS/PBCH block and CORESET #0.

In one example, Pattern 2 can be configured at least for the case wherethe SCS of SS/PBCH block is not the same as the SCS of CORESET #0, e.g.,the SCS of SS/PBCH block is twice of the SCS of CORESET #0 (1101) or theSCS of SS/PBCH block is half of the SCS of CORESET #0 (1102). Anillustration of this example is shown in 1101 and 1102 of FIG. 11 .

FIG. 11 illustrates an example pattern 2 1100 according to embodimentsof the present disclosure. An embodiment of the pattern 2 1100 shown inFIG. 11 is for illustration only.

In another example, Pattern 2 can be configured at least for the casewhere the SCS of SS/PBCH block is the same as the SCS of CORESET #0. Anillustration of this example is shown in 1103 of FIG. 11 .

In one embodiment, as shown in FIG. 12 , the BW of CORESET #0 (e.g.,BW_(CORESET)) and the BW of SSB (e.g., BW_(SSB)) can satisfyBW_(CORESET)+BW_(SSB)+O₁+O₂+P₃=BW_(CH), where BW_(CH) is the channel BW,and can be interpreted as N_(RB) ⁴⁸⁰ if the SCS of CORESET #0 is 480kHz, or as N_(RB) ⁹⁶⁰ if the SCS of CORESET #0 is 960 kHz. O₁ is theoffset between SSB and channel boundary according to the location ofsynchronization raster. O₂ is the offset between SSB and CORESET #0,which may be at least 1 RB if floating sync is supported (e.g., k_(SSB)can be larger than 0), and may be at least one extra RB if the SCS ofSS/PBCH block is not the same as the SCS of CORESET #0. For example, thevalue of O₂ depends on whether k_(SSB) can be larger than 0 or not. O₃is the offset between CORESET #0 and channel boundary, and for oneexample, O₃ can be set as 0 to achieve the maximum CORESET #0 bandwidth.

In such embodiment, as shown in FIG. 12 , the RB offset from a smallestRB index of the CORESET for Type0-PDCCH CSS set to a smallest RB indexof the common RB overlapping with a first RB of the SS/PBCH block can bedetermined as −(BW_(SSB)+O₂), wherein the value of BW_(SSB) and O₂ areboth with respect to the SCS of CORESET #0.

FIG. 12 illustrates an example CORESET #0 BW 1200 for pattern 2 orpattern 3 according to embodiments of the present disclosure. Anembodiment of the CORESET #0 BW 1200 shown in FIG. 12 is forillustration only.

In one example, for Pattern 2 with {SCS_(SSB), SCS_(CORESET)}={960 kHz,960 kHz}, O₁=0, and O₃=0. For one example, the RB offset from thesmallest RB index of the CORESET for Type0-PDCCH CSS set to the smallestRB index of the common RB overlapping with a first RB of the SS/PBCHblock can be determined as −20. For another example, the RB offset froma smallest RB index of the CORESET for Type0-PDCCH CSS set to a smallestRB index of the common RB overlapping with a first RB of the SS/PBCHblock can be determined as −25 if k_(SSB)>0, and determined as −26 ifk_(SSB)=0.

In another example, for Pattern 2 with {SCS_(SSB), SCS_(CORESET)}={960kHz, 960 kHz}, O₃>0. For one example, the RB offset from a smallest RBindex of the CORESET for Type0-PDCCH CSS set to a smallest RB index ofthe common RB overlapping with a first RB of the SS/PBCH block can bedetermined as −21 if k_(SSB)>0, and determined as −20 if k_(SSB)=0. Foranother example, the RB offset from the smallest RB index of the CORESETfor Type0-PDCCH CSS set to the smallest RB index of the common RBoverlapping with a first RB of the SS/PBCH block can be determined as−21.

In yet another example, for Pattern 2 with {SCS_(SSB),SCS_(CORESET)}={480 kHz, 960 kHz}, O₃>0. For one example, the RB offsetfrom a smallest RB index of the CORESET for Type0-PDCCH CSS set to asmallest RB index of the common RB overlapping with a first RB of theSS/PBCH block can be determined as −12 if k_(SSB)>0, and determined as−11 if k_(SSB)=0. For another example, the RB offset from the smallestRB index of the CORESET for Type0-PDCCH CSS set to the smallest RB indexof the common RB overlapping with a first RB of the SS/PBCH block can bedetermined as −12.

In yet another example, for Pattern 2 with {SCS_(SSB),SCS_(CORESET)}={960 kHz, 480 kHz}, O₃>0. For one example, the RB offsetfrom a smallest RB index of the CORESET for Type0-PDCCH CSS set to asmallest RB index of the common RB overlapping with a first RB of theSS/PBCH block can be determined as −42 if k_(SSB)>0, and determined as−41 if k_(SSB)=0. For another example, the RB offset from the smallestRB index of the CORESET for Type0-PDCCH CSS set to the smallest RB indexof the common RB overlapping with a first RB of the SS/PBCH block can bedetermined as −42.

In another embodiment, the number of symbols for CORESET #0 can bedependent on relation between the SCS of CORESET #0 and the SCS ofSS/PBCH block.

In one example, if the SCS of SS/PBCH block is twice of the SCS ofCORESET #0 (e.g., 1101 in FIG. 11 ), the number of symbols for CORESET#0 can be determined as 1 for Pattern 2 (e.g., to leave the number ofsymbols for PDSCH of RMSI as 2).

In another example, if the SCS of SS/PBCH block is half of the SCS ofCORESET #0 (e.g., 1102 in FIG. 11 ), the number of symbols for CORESET#0 can be configurable between 1 and 2 for Pattern 2 (e.g., to leave thenumber of symbols for PDSCH of RMSI as 4).

In yet another example, if the SCS of SS/PBCH block is same as the SCSof CORESET #0 (e.g., 1103 in FIG. 11 ), the number of symbols forCORESET #0 can be configurable between 1 and 2 for Pattern 2 (e.g., toleave the number of symbols for PDSCH of RMSI as 4 or 7).

Example configurations for Pattern 2 with {SCS_(SSB),SCS_(CORESET)}={960 kHz, 960 kHz} are shown in TABLE 13A, and at least asubset from the table can be supported, wherein BW_(max) can be either150 or 144.

TABLE 13A Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {960 kHz, 960 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 2BW_(max) 1 −26 if k_(SSB) = 0, −25 if k_(SSB) > 0 1 2 BW_(max) 2 −26 ifk_(SSB) = 0, −25 if k_(SSB) > 0 2 2 BW_(max) 1 −20 if k_(SSB) = 0, −21if k_(SSB) > 0 3 2 BW_(max) 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 4 296 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 5 2 96 2 −20 if k_(SSB) = 0,−21 if k_(SSB) > 0 6 2 48 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 7 248 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 8 2 24 1 −20 if k_(SSB) = 0,−21 if k_(SSB) > 0 9 2 24 2 −20 if k_(SSB)= 0, −21 if k_(SSB) > 0

Example configurations for Pattern 2 with {SCS_(SSB),SCS_(CORESET)}={480 kHz, 960 kHz} are shown in TABLE 13B, and at least asubset from the table can be supported, wherein BW_(max) can be either162 or 156.

TABLE 13B Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {480 kHz, 960 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 2BW_(max) 1 −16 if k_(SSB) = 0, −15 if k_(SSB) > 0 1 2 BW_(max) 2 −16 ifk_(SSB) = 0, −15 if k_(SSB) > 0 2 2 BW_(max) 1 −11 if k_(SSB) = 0, −12if k_(SSB) > 0 3 2 BW_(max) 2 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 4 296 1 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 5 2 96 2 −11 if k_(SSB) = 0,−12 if k_(SSB) > 0 6 2 48 1 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 7 248 2 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 8 2 24 1 −11 if k_(SSB) = 0,−12 if k_(SSB) > 0 9 2 24 2 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0

Example configurations for Pattern 2 with {SCS_(SSB),SCS_(CORESET)}={960 kHz, 480 kHz} are shown in TABLE 13C, and at least asubset from the table can be supported, wherein BW_(max) can be either264 or 270.

TABLE 13C Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {960 kHz, 480 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 2BW_(max) 1 −77 if k_(SSB) = 0, −76 if k_(SSB) > 0 1 2 BW_(max) 2 −77 ifk_(SSB) = 0, −76 if k_(SSB) > 0 2 2 BW_(max) 1 −41 if k_(SSB) = 0, −42if k_(SSB) > 0 3 2 BW_(max) 2 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 4 2192 1 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 5 2 192 2 −41 if k_(SSB) =0, −42 if k_(SSB) > 0 6 2 96 1 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 72 96 2 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 8 2 48 1 −41 if k_(SSB) =0, −42 if k_(SSB) > 0 9 2 48 2 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 102 24 1 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 11 2 24 2 −41 if k_(SSB) =0, −42 if k_(SSB) > 0

Example configurations for Pattern 2 with {SCS_(SSB),SCS_(CORESET)}={480 kHz, 480 kHz} are shown in TABLE 13D and at least asubset from the table can be supported, wherein BW_(max) can be either264 or 270.

TABLE 13D Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {960 kHz, 480 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 2BW_(max) 1 −52 if k_(SSB) = 0, −51 if k_(SSB) > 0 1 2 BW_(max) 2 −52 ifk_(SSB) = 0, −51 if k_(SSB) > 0 2 2 BW_(max) 1 −20 if k_(SSB) = 0, −21if k_(SSB) > 0 3 2 BW_(max) 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 4 2192 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 5 2 192 2 −20 if k_(SSB) =0, −21 if k_(SSB) > 0 6 2 96 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 72 96 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 8 2 48 1 −20 if k_(SSB) =0, −21 if k_(SSB) > 0 9 2 48 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 102 24 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 11 2 24 2 −20 if k_(SSB) =0, −21 if k_(SSB) > 0

In one embodiment, Pattern 3 can be supported and configured as themultiplexing pattern between SS/PBCH block and CORESET #0, at least forsome of the combinations of SCSs of SS/PBCH block and CORESET #0.

In one example, Pattern 3 can be configured at least for the case wherethe SCS of SS/PBCH block is not the same as the SCS of CORESET #0, e.g.,the SCS of SS/PBCH block is half of the SCS of CORESET #0. Anillustration of this example is shown in 1301 of FIG. 13 .

FIG. 13 illustrates an example pattern 3 1300 according to embodimentsof the present disclosure. An embodiment of the pattern 3 1300 shown inFIG. 13 is for illustration only.

In another example, Pattern 3 can be configured at least for the casewhere the SCS of SS/PBCH block is the same as the SCS of CORESET #0. Anillustration of this example is shown in 1302 of FIG. 13 .

In one embodiment, the determination of the BW of CORESET #0 (e.g.,BW_(CORESET)) can be similar to Pattern 2 in this disclosure, e.g.,BW_(CORESET)+BW_(SSB)+O₁+O₂+O₃=BW_(CH), and the RB offset from asmallest RB index of the CORESET for Type0-PDCCH CSS set to a smallestRB index of the common RB overlapping with a first RB of the SS/PBCHblock can be determined as −(BW_(SSB)+O₂), wherein the value of BW_(SSB)and O₂ are both with respect to the SCS of CORESET #0. An example isshown in FIG. 12 .

Example configurations for Pattern 3 with {SCS_(SSB), SCS_(CORESET)}={960 kHz, 960 kHz} are shown in TABLE 14A, and at least a subset fromthe table can be supported, wherein BW_(max) can be either 150 or 144.

TABLE 14A Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {960 kHz, 960 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 3BW_(max) 1 −26 if k_(SSB) = 0, −25 if k_(SSB) > 0 1 3 BW_(max) 2 −26 ifk_(SSB) = 0, −25 if k_(SSB) > 0 2 3 BW_(max) 1 −20 if k_(SSB) = 0, −21if k_(SSB) > 0 3 3 BW_(max) 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 4 396 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 5 3 96 2 −20 if k_(SSB) = 0,−21 if k_(SSB) > 0 6 3 48 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 7 348 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 8 3 24 1 −20 if k_(SSB) = 0,−21 if k_(SSB) > 0 9 3 24 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0

Example configurations for Pattern 3 with {SCS_(SSB),SCS_(CORESET)}={480 kHz, 960 kHz} are shown in TABLE 14B, and at least asubset from the table can be supported, wherein BW_(max) can be either162 or 156.

TABLE 14B Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {480 kHz, 960 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 3BW_(max) 1 −16 if k_(SSB) = 0, −15 if k_(SSB) > 0 1 3 BW_(max) 2 −16 ifk_(SSB) = 0, −15 if k_(SSB) > 0 2 3 BW_(max) 1 −11 if k_(SSB) = 0, −12if k_(SSB) > 0 3 3 BW_(max) 2 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 4 396 1 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 5 3 96 2 −11 if k_(SSB) = 0,−12 if k_(SSB) > 0 6 3 48 1 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 7 348 2 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0 8 3 24 1 −11 if k_(SSB) = 0,−12 if k_(SSB) > 0 9 3 24 2 −11 if k_(SSB) = 0, −12 if k_(SSB) > 0

Example configurations for Pattern 2 with {SCS_(SSB),SCS_(CORESET)}={960 kHz, 480 kHz} are shown in TABLE 14C, and at least asubset from the table can be supported, wherein BW_(max) can be either264 or 270.

TABLE 14C Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {960 kHz, 480 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 3BW_(max) 1 −77 if k_(SSB) = 0, −76 if k_(SSB) > 0 1 3 BW_(max) 2 −77 ifk_(SSB) = 0, −76 if k_(SSB) > 0 2 3 BW_(max) 1 −41 if k_(SSB) = 0, −42if k_(SSB) > 0 3 3 BW_(max) 2 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 4 3192 1 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 5 3 192 2 −41 if k_(SSB) =0, −42 if k_(SSB) > 0 6 3 96 1 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 73 96 2 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 8 3 48 1 −41 if k_(SSB) =0, −42 if k_(SSB) > 0 9 3 48 2 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 103 24 1 −41 if k_(SSB) = 0, −42 if k_(SSB) > 0 11 3 24 2 −41 if k_(SSB) =0, −42 if k_(SSB) > 0

Example configurations for Pattern 3 with {SCS_(SSB),SCS_(CORESET)}={480 kHz, 480 kHz} are shown in TABLE 14D and at least asubset from the table can be supported, wherein BW_(max) can be either264 or 270.

TABLE 14D Example CORESET #0 configuration for {SCS_(SSB),SCS_(CORESET)} = {480 kHz, 480 kHz} Multiplexing CORESET#0 No. ofsymbols RB-level offset Index pattern BW (RB) for CORESET #0 (RB) 0 3BW_(max) 1 −52 if k_(SSB) = 0, −51 if k_(SSB) > 0 1 3 BW_(max) 2 −52 ifk_(SSB) = 0, −51 if k_(SSB) > 0 2 3 BW_(max) 1 −20 if k_(SSB) = 0, −21if k_(SSB) > 0 3 3 BW_(max) 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 4 3192 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 5 3 192 2 −20 if k_(SSB) =0, −21 if k_(SSB) > 0 6 3 96 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 73 96 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 8 3 48 1 −20 if k_(SSB) =0, −21 if k_(SSB) > 0 9 3 48 2 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 103 24 1 −20 if k_(SSB) = 0, −21 if k_(SSB) > 0 11 3 24 2 −20 if k_(SSB) =0, −21 if k_(SSB) > 0

The present disclosure focuses on an initial access in carrieraggregation scenario. In particular, the embodiments of this disclosureare at least applicable to operation with shared spectrum channelaccess. The present disclosure includes channelization of carriers,common resource grid, synchronization raster design, and cross-carrierCORESET #0 design.

For a new carrier frequency range between 52.6 GHz and 71 GHz, there isa need to support a large operating bandwidth, e.g., as large as atleast 2.16 GHz, to coexist with Wi-Fi operating on the same carrierfrequency range. In one example, the large bandwidth can be achieved bycarrier aggregation from multiple carriers with smaller carrierbandwidth (e.g., 400 MHz). This disclosure specifies the details ofdesign examples regarding the initial access procedure using carrieraggregation. An illustration of using carrier aggregation to achievelarge operating bandwidth is shown in FIG. 14 .

FIG. 14 illustrates an example carrier aggregation 1400 to achieve largebandwidth according to embodiments of the present disclosure. Anembodiment of the carrier aggregation 1400 shown in FIG. 14 is forillustration only.

In this disclosure, CORESET #0 refers to the control resource set(CORESET) of the Type0-PDCCH common search space set.

In one embodiment, a wideband (e.g., with a bandwidth of 2.16 GHz ormore) can be operated with carrier aggregation from a set of narrowcarriers (e.g., each narrow carrier with a bandwidth smaller than 2.16GHz).

In one example, the set of narrow carriers can include at least oneexample from TABLE 15, and illustration of the examples is shown in FIG.15 . In one example, a narrow carrier with a given bandwidth isassociated with a minimum subcarrier spacing. For one example, 400 MHzbandwidth is associated with a minimum subcarrier spacing of 120 kHz;for another example, 800 MHz bandwidth is associated with a minimumsubcarrier spacing of 240 kHz; for yet another example, 1200 MHz or 1600kHz is associated with a minimum subcarrier spacing of 480 kHz.

FIG. 15 illustrates an example set of narrow carriers 1500 to constructwideband using carrier aggregation according to embodiments of thepresent disclosure. An embodiment of the set of narrow carriers 1500shown in FIG. 15 is for illustration only.

TABLE 15 Examples of the set of narrow carriers to construct widebandusing carrier aggregation. Example # Bandwidth of the set of narrowcarriers (MHz) 1 {400, 400, 400, 400, 400} 2 {800, 400, 400, 400} 3{400, 800, 400, 400} 4 {400,400, 800, 400} 5 {400, 400, 400, 800} 6{800, 800, 400} 7 {800, 400, 800} 8 {400, 800, 800} 9 {1200, 800} 10{800, 1200} 11 {400, 1600} 12 {1600, 400}

In one example, for a targeted wideband, the set of narrow carriers toconstruct the wideband using carrier aggregation can utilize a fixedchannelization, in the sense that the center of the narrow carriers isfixed. For instance, each of the narrow carriers constructing thewideband in an example of TABLE 15 has a fixed carrier center specified.

In one example, the fixed channelization is applicable to operation withshared spectrum channel access.

In another embodiment, for a targeted wideband, the set of narrowcarriers to construct the wideband using carrier aggregation can beconfigurable, and location of the narrow carriers are indicated to theUE.

In one example, the fixed channelization is applicable to operationwithout shared spectrum channel access.

In one example, the set of narrow carriers are using the same subcarrierspacing and same common resource grid. For example, the common resourcegrids of the set of narrow carriers are determined from the same PointA.

In one example, the guard bands for the set of narrow carriers areinteger number of RBs in term of the SCS of the common resource grid.For one example, if the channelization of the set of narrow carriers isfixed, the guard bands for the set of narrow carriers are also fixedinteger number of RBs. For another example, if the channelization of theset of narrow carriers is configured, the guard bands for the set ofnarrow carriers are also configurable as an integer number of RBs.

In one example, for operation with shared spectrum channel access, eachcarrier of the set of narrow bands has a single synchronization rasterpoint.

In one example, the single synchronization raster point corresponds to aglobal synchronization channel number (GSCN).

In another example, for operation without shared spectrum channelaccess, each carrier of the set of narrow bands has at least onesynchronization raster point.

In one example, the at least one synchronization raster pointcorresponds to GSCN(s).

In one example, the set of synchronization raster points for operationwith shared spectrum channel access (e.g., unlicensed operation) is asubset of the set of synchronization raster points for operation withoutshared spectrum channel access (e.g., licensed operation).

An illustration of this example is shown in FIG. 16 (e.g., asillustrated in (a)). For this example, the total number ofsynchronization raster points for the wideband can be smaller, and a UEdoesn't need to rely on the location of the synchronization rasterpoints to distinguish licensed or unlicensed operations. If a UE detectsa SS/PBCH block located on the synchronization raster point for bothlicensed and unlicensed operations, the UE can distinguish the SS/PBCHblock is with licensed or unlicensed operations based on otherindication.

FIG. 16 illustrates an example synchronization raster design 1600 forunlicensed and licensed operations according to embodiments of thepresent disclosure. An embodiment of the synchronization raster design1600 shown in FIG. 16 is for illustration only.

In another example, the set of synchronization raster points foroperation with shared spectrum channel access (e.g., unlicensedoperation) does not overlap with the set of synchronization rasterpoints for operation without shared spectrum channel access (e.g.,licensed operation). The GSCN values corresponding to the set ofsynchronization raster points for operation with shared spectrum channelaccess are different from the GSCN values corresponding to the set ofsynchronization raster points for operation without shared spectrumchannel access.

An illustration of this example is shown in FIG. 16 (e.g., asillustrated in (b)). For this example, the UE can distinguish thedetected SS/PBCH is with licensed or unlicensed operation based on thesynchronization raster value.

In one example, when a set of narrow carriers construct a wideband usingcarrier aggregation, and a SS/PBCH block is detected in one of thenarrow carriers within the set of narrow carriers, the associatedCORESET #0 of the SS/PBCH block can be configured to locate in anothernarrow carrier within the set of narrow carriers. For example, withinthe set of configurations for CORESET #0 by MIB, there is at least oneconfiguration corresponding to a cross-carrier CORESET #0.

In one example, the initial DL BWP is not located within the samecarrier as the detected SSB, wherein the BW of the initial DL BWP issame as the BW of CORESET #0.

In another example, the cross-carrier CORESET #0 is only applicable tothe multiplexing pattern of CORESET #0 and SS/PBCH block as Pattern 2 orPattern 3.

In yet another example, the offset from a smallest RB index of theCORESET for Type0-PDCCH CSS set (e.g., CORESET #0) to a smallest RBindex of the common RB overlapping with a first RB of the detectedSS/PBCH block can be indicated by MIB of the detected SS/PBCH block. Anillustration of this example is shown in FIG. 17A and FIG. 17B.

FIG. 17A illustrates an example cross-carrier indication 1700 forCORESET #0 according to embodiments of the present disclosure. Anembodiment of the cross-carrier indication 1700 shown in FIG. 17A is forillustration only.

FIG. 17B illustrates another example cross-carrier indication 1750 forCORESET #0 according to embodiments of the present disclosure. Anembodiment of the cross-carrier indication 1750 shown in FIG. 17B is forillustration only.

In one example, if the set of narrow carriers have the same commonresource grid, the quantity k_(SSB) is the subcarrier offset fromsubcarrier 0 in common resource block N_(CRB) ^(SSB) to subcarrier 0 ofthe SS/PBCH block, wherein the center of subcarrier 0 of resource blockN_(CRB) ^(SSB) coincides with the center of subcarrier 0 of a commonresource block.

In another example, if there is no requirement on the alignment ofcommon resource grid, the quantity k_(SSB) is the subcarrier offset fromsubcarrier 0 in common resource block N_(CRB) ^(SSB) to subcarrier 0 ofthe SS/PBCH block, wherein the center of subcarrier 0 of resource blockN_(CRB) ^(SSB) coincides with the center of subcarrier 0 of a commonresource block for the carrier containing CORESET #0.

In one example, as shown in FIG. 17A, CORESET #0 locates in a carrierwith higher frequency than the carrier containing the detected SS/PBCHblock. Denote the carriers in the lower to higher frequency indexed from1 to n (e.g., n=3 in FIG. 17A), and the detected SS/PBCH block locatesin carrier with index 1, while CORESET #0 locates in carrier with indexn (e.g., n>1), then the frequency offset from a smallest RB index of theCORESET #0 to a smallest RB index of the common RB overlapping with afirst RB of the detected SS/PBCH block can be given by Equation 1.

$\begin{matrix}{\Delta_{{SSB} - {{CORESET}{\# 0}}} = {{\underset{i = 1}{\sum\limits^{n - 1}}( {{BW}_{i}^{c} + {BW}_{i,{i + 1}}^{g}} )} + \Delta_{{CORESET}{\# 0}} - \Delta_{SSB}}} & {{equation}1}\end{matrix}$

In Equation 1, BW_(i) ^(c) is the bandwidth of carrier with index i inthe unit of RB with respect to the SCS of CORESET #0, BW_(i,i+1) ^(g) isthe bandwidth of guard bandwidth between neighboring carriers withindexes i and i+1 in the unit of RB with respect to the SCS of CORESET#0, Δ_(CORESET #0) is the offset from the smallest RB index of theCORESET #0 to the smallest RB index of the carrier (e.g., carrier withindex n) containing CORESET #0, and Δ_(SSB) is the offset from thesmallest RB index of the common RB overlapping with a first RB of thedetected SS/PBCH block to the smallest RB index of the carrier (e.g.,carrier with index 1) containing SS/PBCH block.

In another example, as shown in FIG. 17B, CORESET #0 locates in acarrier with lower frequency than the carrier containing the detectedSS/PBCH block. Denote the carriers in the lower to higher frequencyindexed from 1 to n (e.g., n=3 in FIG. 17B), and the detected SS/PBCHblock locates in carrier with index n (e.g., n>1), while CORESET #0locates in carrier with index 1, then the frequency offset from asmallest RB index of the CORESET #0 to a smallest RB index of the commonRB overlapping with a first RB of the detected SS/PBCH block can begiven by Equation 2.

$\begin{matrix}{\Delta_{{SSB} - {{CORESET}{\# 0}}} = {{\underset{i = 1}{\sum\limits^{n - 1}}( {{BW}_{i}^{c} + {BW}_{i,{i + 1}}^{g}} )} + \Delta_{{CORESET}{\# 0}} - \Delta_{SSB}}} & {{equation}2}\end{matrix}$

In Equation 2, BW_(i) ^(c) is the bandwidth of carrier with index i inthe unit of RB with respect to the SCS of CORESET #0, BW_(i,i+1) ^(g) isthe bandwidth of guard bandwidth between neighboring carriers withindexes i and i+1 in the unit of RB with respect to the SCS of CORESET#0, Δ_(CORESET #0) is the offset from the smallest RB index of theCORESET #0 to the smallest RB index of the carrier (e.g., carrier withindex 1) containing CORESET #0, and Δ_(SSB) is the offset from thesmallest RB index of the common RB overlapping with a first RB of thedetected SS/PBCH block to the smallest RB index of the carrier (e.g.,carrier with index n) containing SS/PBCH block.

In one example, Δ_(SSB) can be determined as 0.

In one example, Δ_(CORESET #0) can be determined as 0.

In one example, when the channelization of the set of narrow carriers isfixed, and the location of a CORESET #0 within a carrier is also fixed(e.g., Δ_(CORESET #0) is fixed and known to the UE), the UE can derivethe offset Δ_(SSB-CORESET #0) according to Equation 1 or Equation 2 andthere is no need for an explicit indication of the offset value.

In another example, when the channelization of the set of narrowcarriers is fixed, the UE can be provided with an index of the carrierfor CORESET #0, and the UE can derive the offset Δ_(SSB-CORESET #0)according to Equation 1 or Equation 2 and there is no need for anexplicit indication of the offset value. For one sub-example, Equation 1or Equation 2 can be simplified as Equation 3, wherein Δ₁ is the numberof RB for the carrier with smallest bandwidth within the set of narrowcarriers together with the guard band (e.g., Δ₁=BW_(i) ^(c)+BW_(i,i+1)^(g)), Δ₂=Δ_(CORESET #0)−Δ_(SSB), and the index k is provided by the gNBand indicated to the UE (e.g., by PBCH payload). k can be eitherpositive or negative, corresponding to Equation 1 or Equation 2respectively.Δ_(SSB-CORESET #0) =k·Δ ₁+Δ₂  equation 3

In yet another example, the UE is configured with an offset valueexplicitly by MIB, wherein the offset value can be jointly coded withother parameters for CORESET #0, e.g., multiplexing pattern with SS/PBCHblock, number of symbols for CORESET #0, and/or bandwidth of CORESET #0.For instance, at least one example from TABLE 16, where Δ₁ is the numberof RB for the carrier with smallest bandwidth within the set of narrowcarriers together with the guard band (e.g., Δ_(i)=BW_(i)^(c)+BW_(i,i+1) ^(g)), and Δ₂=Δ_(CORESET #0)−Δ_(SSB)

TABLE 16 Example of cross-carrier CORESET#0 configuration provided byMIB. Multi- No. of RB-level offset plexing CORESET#0 symbols forΔ_(SSB-CORESET#0) Index pattern BW (RB) CORESET #0 (RB) 0 2 or 3 24 or48 or 96 1 or 2  Δ₁ + Δ₂ 1 2 or 3 24 or 48 or 96 1 or 2 2Δ₁ + Δ₂ 2 2 or3 24 or 48 or 96 1 or 2 3Δ₁ + Δ₂ 3 2 or 3 24 or 48 or 96 1 or 2 4Δ₁ + Δ₂4 2 or 3 24 or 48 or 96 1 or 2 −Δ₁ + Δ₂ 5 2 or 3 24 or 48 or 96 1 or 2−2Δ₁ + Δ₂  6 2 or 3 24 or 48 or 96 1 or 2 −3Δ₁ + Δ₂  7 2 or 3 24 or 48or 96 1 or 2 −4Δ₁ + Δ₂ 

In yet another example, the UE is configured with an offset provided byMIB of the detected SS/PBCH block, and the UE is further provided withinformation of the carrier containing the CORESET #0 (e.g., by PBCHpayload), then the UE can derive the frequency offset from a smallest RBindex of the CORESET #0 to a smallest RB index of the common RBoverlapping with a first RB of the detected SS/PBCH block by owncalculation based on the indicated offset from MIB and information ofthe carrier containing CORESET #0 (no need for explicit indication ofthe offset value). In this example, Equation 4 can be used, as asimplification of Equation 1 or Equation 2, wherein Δ₃ is the offsetprovided by MIB, Δ₁ is the number of RB for the carrier with smallestbandwidth within the set of narrow carriers together with the guard band(e.g., Δ₁=BW_(i) ^(c)+BW_(i,i+1) ^(g)), and k is the carrier indexdifference. k can be either positive or negative, corresponding toEquation 1 or Equation 2 respectively.Δ_(SSB-CORESET #0) =k·Δ ₁+Δ₃  equation 4

In one example, Δ₁=284 when the SCS of type0-PDCCH within CORESET #0 is120 kHz, Δ₁=142 when the SCS of type0-PDCCH within CORESET #0 is 240kHz, Δ₁=71 or 72 when the SCS of type0-PDCCH within CORESET #0 is 480kHz.

In another example of above examples, Δ₂=0.

In yet another example, Δ₂=0 if the SCS of SS/PBCH block is the same asthe SCS of type0-PDCCH within CORESET #0, andΔ₂=−10·SCS_(SSB)/SCS_(CORESET #0), wherein SCS_(SSB) is the SCS ofSS/PBCH block, and SCS_(CORESET #0) is the SCS of the SCS of type0-PDCCHwithin CORESET #0.

In yet another example, k is directly indicated (e.g., by PBCH payload)as one value from k∈{−3, −2, −1, 0, 1, 2, 3}.

In yet another example of above examples, UE is provided with an indexof the carrier containing CORESET #0 and determines the carrier indexdifference between the carrier containing CORESET #0 and the carriercontaining the detected SS/PBCH block, e.g., to determine the value of ksuch that k∈{−3, −2, −1, 0, 1, 2, 3}.

FIG. 18 illustrates a flow chart of a method 1800 for determining PBCHcontent according to embodiments of the present disclosure, as may beperformed by UE (e.g., as 111-116 as illustrated in FIG. 1 ). Acorresponding and complementary process may be performed by a BS, suchas BS 102 in FIG. 1 . An embodiment of the method 1800 shown in FIG. 18is for illustration only. One or more of the components illustrated inFIG. 18 can be implemented in specialized circuitry configured toperform the noted functions or one or more of the components can beimplemented by one or more processors executing instructions to performthe noted functions.

The method begins with the UE receiving SS/PBCH block (step 1802). Forexample, in step 1802, the UE SS/PBCH block may be received from the BS.The UE then decodes content of a PBCH in the SS/PBCH block (step 1804).

Thereafter, the UE determines whether the wireless communication systemoperates with shared spectrum channel access (step 1806). For example,in step 1806, the UE determines whether the wireless communicationsystem operates with shared spectrum channel access based on the decodedcontent of the PBCH. In one example, the wireless communication systemis determined as operating with shared spectrum channel access, if a QCLparameter (N_(SSB) ^(QCL)) in the content of the PBCH is determined as anumerical value. In another example, the wireless communication systemis determined as operating without shared spectrum channel access, ifthe QCL parameter (N_(SSB) ^(QCL)) in the content of the PBCH isdetermined as a non-numerical value.

If the UE determines that wireless communication system operates withshared spectrum channel access, the UE determines the content of thePBCH in a first manner (step 1808). For example, in step 1808, for thefirst manner of determining the content of the PBCH, the UE determines abit (ā_(Ā)) in the content of the PBCH as a seventh LSB of a candidateSS/PBCH block index. In another example, for the first manner ofdetermining the content of the PBCH, the UE determines a first field inMIB in the content of the PBCH as a fourth LSB of a SFN. In anotherexample, for the first manner of determining the content of the PBCH,the UE determines a second field in MIB in the content of the PBCH as aconfiguration of a CORESET for monitoring a Type0-PDCCH. In one example,the configuration of the CORESET includes a multiplexing pattern betweenthe CORESET and the SS/PBCH block and the multiplexing pattern is onefrom a first, a second, or a third pattern for a combination of a SCS ofthe CORESET and a SCS of the SS/PBCH block. In another example, whereinthe configuration of the CORESET includes a frequency offset from afirst resource block of the CORESET to a first resource block of theSS/PBCH block.

If, however, the UE determines that wireless communication systemoperates without shared spectrum channel access, the UE determines thecontent of the PBCH in a second manner (step 1810). For example, in step1810, the UE may determine the content of the PBCH differently than thefirst manner discussed above.

The above flowcharts illustrate example methods that can be implementedin accordance with the principles of the present disclosure and variouschanges could be made to the methods illustrated in the flowchartsherein. For example, while shown as a series of steps, various steps ineach figure could overlap, occur in parallel, occur in a differentorder, or occur multiple times. In another example, steps may be omittedor replaced by other steps.

Although the present disclosure has been described with exemplaryembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims. None of the description in this application should be read asimplying that any particular element, step, or function is an essentialelement that must be included in the claims scope. The scope of patentedsubject matter is defined by the claims.

What is claimed is:
 1. A user equipment (UE) in a wireless communicationsystem, the UE comprising: a transceiver configured to receive asynchronization signal and physical broadcast channel (SS/PBCH) block,and a processor operably connected to the transceiver, the processorconfigured to: decode content of a PBCH in the SS/PBCH block; determinewhether the wireless communication system operates with shared spectrumchannel access based on a first portion of the content of the PBCH;determine a second portion of the content of the PBCH in a first manner,if the wireless communication system operates with shared spectrumchannel access; and determine the second portion of the content of thePBCH in a second manner, if the wireless communication system operateswithout shared spectrum channel access.
 2. The UE of claim 1, wherein:the wireless communication system is determined as operating with sharedspectrum channel access, if a QCL parameter (N_(SSB) ^(QCL)) in thecontent of the PBCH is determined as a numerical value; and the wirelesscommunication system is determined as operating without shared spectrumchannel access, if the QCL parameter (N_(SSB) ^(QCL)) in the content ofthe PBCH is determined as a non-numerical value.
 3. The UE of claim 1,wherein the first manner of determining the second portion of thecontent of the PBCH includes determining a bit (ā_(Ā)) in the secondportion of the content of the PBCH as a seventh lowest significant bit(LSB) of a candidate SS/PBCH block index.
 4. The UE of claim 1, whereinthe first manner of determining the second portion of the content of thePBCH includes determining a first field in master information block(MIB) in the second portion of the content of the PBCH as a fourthlowest significant bit (LSB) of a system frame number (SFN).
 5. The UEof claim 1, wherein the first manner of determining the second portionof the content of the PBCH includes determining a second field in MIB inthe second portion of the content of the PBCH as a configuration of acontrol resource set (CORESET) for monitoring a Type0 physical downlinkcontrol channel (Type0-PDCCH).
 6. The UE of claim 5, wherein: theconfiguration of the CORESET includes a multiplexing pattern between theCORESET and the SS/PBCH block, and the multiplexing pattern is one froma first, a second, or a third pattern for a combination of a sub-carrierspacing (SCS) of the CORESET and a SCS of the SS/PBCH block.
 7. The UEof claim 5, wherein the configuration of the CORESET includes afrequency offset from a first resource block of the CORESET to a firstresource block of the SS/PBCH block.
 8. A base station (BS) in awireless communication system, the BS comprising: a processor configuredto: determine whether the wireless communication system operates withshared spectrum channel access; configure a first portion of content ofa physical broadcast channel (PBCH) to determine whether the wirelesscommunication system operates with shared spectrum channel access;configure a second portion of the content of the PBCH according to afirst manner, if the wireless communication system operates with sharedspectrum channel access; configure the second portion of the content ofthe PBCH according to a second manner, if the wireless communicationsystem operates without shared spectrum channel access; and encode theconfigured first and second portions content of the PBCH in asynchronization signal and physical broadcast channel (SS/PBCH) block;and a transceiver operably connected to the processor, the transceiverconfigured to transmit the SS/PBCH block over downlink channels.
 9. TheBS of claim 8, wherein: if the wireless communication system isdetermined as operating with shared spectrum channel access, a QCLparameter (N_(SSB) ^(QCL)) is included in the content of the PBCH as anumerical value; and if the wireless communication system is determinedas operating without shared spectrum channel access, the QCL parameter(N_(SSB) ^(QCL)) is included in the content of the PBCH as anon-numerical value.
 10. The BS of claim 8, wherein the first manner ofdetermining the second portion of the content of the PBCH includesdetermining a bit (ā_(Ā)) in the second portion of the content of thePBCH as a seventh lowest significant bit (LSB) of a candidate SS/PBCHblock index.
 11. The BS of claim 8, wherein the first manner ofdetermining the second portion of the content of the PBCH includesdetermining a first field in master information block (MIB) in thesecond portion of the content of the PBCH as a fourth lowest significantbit (LSB) of a system frame number (SFN).
 12. The BS of claim 8, whereinthe first manner of determining the second portion of the content of thePBCH includes determining a second field in MIB in the second portion ofthe content of the PBCH as a configuration of a control resource set(CORESET) for monitoring Type₀ physical downlink control channel(Type0-PDCCH).
 13. The BS of claim 12, wherein: the configuration of theCORESET includes a multiplexing pattern between the CORESET and theSS/PBCH block, the multiplexing pattern is one from a first, a second,or a third pattern for a combination of a sub-carrier spacing (SCS) ofthe CORESET and a SCS of the SS/PBCH block, and a frequency offset froma first resource block of the CORESET to a first resource block of theSS/PBCH block.
 14. A method of a user equipment (UE) in a wirelesscommunication system, the method comprising: receiving a synchronizationsignal and physical broadcast channel (SS/PBCH) block; decoding acontent of a PBCH in the SS/PBCH block; determining whether the wirelesscommunication system operates with shared spectrum channel access basedon a first portion of the content of the PBCH; and determining a secondportion of the content of the PBCH in a first manner based ondetermining that the wireless communication system operates with sharedspectrum channel access or determining the second portion of the contentof the PBCH in a second manner based on determining that the wirelesscommunication system operates without shared spectrum channel access.15. The method of claim 14, wherein: the wireless communication systemis determined as operating with shared spectrum channel access based ondetermining that a QCL parameter (N_(SSB) ^(QCL)) in the content of thePBCH is a numerical value; or the wireless communication system isdetermined as operating without shared spectrum channel access based ondetermining that the QCL parameter (N_(SSB) ^(QCL)) in the content ofthe PBCH is a non-numerical value.
 16. The method of claim 14, whereinthe first manner of determining the second portion of the content of thePBCH includes determining a bit (ā_(Ā)) in the second portion of thecontent of the PBCH as a seventh lowest significant bit (LSB) of acandidate SS/PBCH block index.
 17. The method of claim 14, wherein thefirst manner of determining the second portion of the content of thePBCH includes determining a first field in master information block(MIB) in the second portion of the content of the PBCH as a fourthlowest significant bit (LSB) of a system frame number (SFN).
 18. Themethod of claim 14, wherein the first manner of determining the secondportion of the content of the PBCH includes determining a second fieldin MIB in the second portion of the content of the PBCH as aconfiguration of a control resource set (CORESET) for monitoring a Type0physical downlink control channel (Type0-PDCCH).
 19. The method of claim18, wherein: the configuration of the CORESET includes a multiplexingpattern between the CORESET and the SS/PBCH block, and the multiplexingpattern is one from a first, a second, or a third pattern for acombination of a sub-carrier spacing (SCS) of the CORESET and a SCS ofthe SS/PBCH block.
 20. The method of claim 18, wherein the configurationof the CORESET includes a frequency offset from a first resource blockof the CORESET to a first resource block of the SS/PBCH block.